"Paul" <Paul@discussions.microsoft.com> wrote in message
news:F23EBDCE-94BC-400D-B55F-AC7FE7DEA425@microsoft.com:
> Thank you everyone for your responses.
>
> As it turns out, it was a permissions problem (isn't it always). The sa user
> didn't have the proper permissions to the view which I was extracting data
> from.
>
> The DTS was fine.
>
> Thanks.
>
>
>
>
> "Allan Mitchell" wrote:
>
> > Russel
> >
> > If you test the transform then you get the same window up that you get
> > when using an AX transform. There is a "View Results" button there
> >
> > Do any rows get returned when you execute the package as a whole?
> >
> > --
> >
> >
> > Allan Mitchell
> >
http://wiki.sqlis.com |
http://www.sqlis.com |
http://www.sqldts.com |
> >
http://www.konesans.com > >
> >
> >
> >
> > "RLoski" <RLoski@discussions.microsoft.com> wrote in message
> > news:D3224D56-1B73-4DF4-87E0-F2694BAD9D14@microsoft.com:
> >
> > > Could you help me? I can't recall where or when the "View Results" button
> > > displays.
> > > --
> > > Russel Loski, MCSD.Net
> > >
> > >
> > > "Paul" wrote:
> > >
> > > > I am trying to write my first DTS in SQL Server 2000.
> > > >
> > > > It is a very simple DTS. All it does is execute a query from a table in SQL
> > > > Server A and copy the results (transform data task) to a table in SQL Server
> > > > B. I am sure the query is good because I tested it.
> > > >
> > > > So, using DTS Designer, I use SQL Server authentication for Connection A and
> > > > use the "sa" account. I also use SQL Server authentication for Connection B
> > > > and use the "sa" account.
> > > >
> > > > I use a Transform Data task for the query. I then go to the Transformations
> > > > tab of the task and click the "test" button for each transformation.
> > > >
> > > > The Package Execution Results says that the package was successfully
> > > > completed.
> > > >
> > > > But then I click the "View Results" button and no results are returned for
> > > > that column? This is true for all the columns.
> > > >
> > > > That is the problem.
> > > >
> > > > Is this a permissions problem with the "sa" account?
> >
> >