Wouldn't I need two sets of databases for that?

It is what I have used in the past but the database is still in constant change and there is a lot of internal opposition to replication. I would not...

Greg,

You are right! That was the problem. The connection to SQL within the package was using Windows login.

Thanks,

Ed:)

The actual error is

DTSRun: Loading...

DTSRun: Executing...

DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1

DTSRun OnStart: DTSStep_DTSDataPumpTask_3

DTSRun OnStart: DTSStep_DTSDataPumpTask_4

DTSRun OnStart: DTSStep_DTSDataPumpTask_5

DTSRun OnError: DTSStep_DTSDataPumpTask_5, Error = -2147217843 (80040E4D)

Error...

The SQL user does have those rights but, from the users workstation, it is giving an error that his Windows login does not have rights. It works from mine but...

Gail,

In the sys.dm_db_index_usage_stats DMV some object id's are returned that do not return a name when passed to the OBJECT_NAME function. Why would that be?

Thanks,

Ed

Thanks, Gail, I'm glad we finally moved this application to 2005. I keep finding or being alerted to new useful features to make my life easier.

Ed

Hi Brian,

From the execution plan it appears to be using indexes that might not be needed. We are currently in the planning stages of a comprehensive set of tests that...

Hi Gail,

This is old code that surfaces now that we have moved to SQL Server 2005. It is kept in the middle tier, there is a lot of resistance from...

If I don't put the subquery in the SELECT the performance degrades terribly. FYI, the left table has 250 rows & right has ~1 million. I have attached, in...

It now runs making a command call to dtsrun from the computer where the outside application runs. Since that computer has access to the path, it runs flawlessly.

Thanks,

Ed

Hi Jez,

In that case, since the stored procedure is called by a sql login it takes the security context of the caller or none at all since it is not...

You were right, applying SP2 made the issue go away. Now I can edit the packages again.

Thanks,

Ed

Ed,

I didn't use the Import Wizard. What I did was create a SSIS job that copied the packages from the 2000 msdb to the 2005 one. That's probably the reason...

Thanks, Ed. I did the original migration by doing a data flow in SSIS from the old msdb to the 2005 msdb. They were editable then. I have one package...