Aint that the truth!

Andy

Maybe a version problem? There are different objects for SQL7 and SQL2K, most of the SQL2K ones have a '2' appended.

Andy

I think what you need to change is located in the following registry key:

hkey_local_machine\software\microsoft\MSSQLServer\Client\SuperSocketNetLib

You should find a value there for Protocol order, on my machine it lists it as follows:

tcp...

Try starting a transaction, then do a select, then use a waitfor to force a delay.

Andy

If you install the client tools or the entire SQL install you'll get the client configuration utility. You can use that to change the default. Are you having problems connecting...

Retreif - I agree. You either have to spend extra time (possibly anyway) when you build it to make it portable or live with the consequences if/when you have to...

If you build normalized structures and run adequate hardware speed will never be an issue in my experience. I'd go with option number one for sure.

Andy

Depends on how many you're moving doesn't it? I wrote this after someone asked for help moving more than 200 packages.

Andy

You might want to look at a later article I did that covers a VB add in that will generate the command object code for you, a real time saver....

DMO is another alternative, though sp_start_job, etc, are just as good if that's all you're doing.

Andy

Should work unless there was more than once log file.

Andy

Havent tried it for client tools but might work, take a look at unattended installation in BOL. For the client setting should be able to just push a .reg file...

I dont remember seeing one, will look around some.

Andy

I vote for one partition.

Andy

I usually do this with two separate queries, one a left join and one a right join.

Andy