I think you can just put osql.exe on the workstation and then use the osql switches to have it connect to the SQL Server..

For example you'll specify the following (can...

SQL 2005 defaults to Windows Authentication only I think.  Sonds to me like you have that security setting and what you're looking for is to have it set to Windows...

I think the impact on the SQL server from the monitoring should be fairly minimal.. there is impact though so you could also do the monitoring from another server and...

Not sure you're specific errors, but I too have seen sqlsrv.exe process taking up to 2 GB (which is the max that SQL 2000 Standard can use (not sure what...

I haven't used SQL 7.0 in a long time and I rarely use DTS, but I have seen that kind of error before when SQL security authentication is set to Windows...

When you are copying from one sql2k5 server to another then the Copy Database Wizard should include another screen that allows you to specify 'Additional database object to transfer'.  Sounds...

Seems to me you should just use the Enterprise Manager Maintenance Plan Wizard to create this.  Just have it create a Transaction log backup only- specifying the schedule and backup...

It's available already:

http://www.microsoft.com/sql/sp1.mspx

In fact, I was reading that Microsoft is already planning hotfixes for SP1:

http://weblog.infoworld.com/dbunderground/archives/2006/05/microsoft_plans.html

If you are planning to upgrade (and not do a clean install) I would...

I haven't had need for that yet so I have not looked for it, but I thought that post said it was a fix in SP1.  You're using that now?

You can see some responses to this same question here (including my answer re-copied below):

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=275594#bm275806

- I have not seen this option in the SQL 2005 "Maintenance Plan Wizard" but...

I was under the impression that SQL 2005 db could not go back to SQL 2000.. I am really not sure.. maybe you can do something at the table level? ...

I am not sure how you were planning to move the databases from Old Server to New Server (there are different options for that) - but I would think if...

Personally I have had some issues with upgrading to SP1 (like the above links and more), but no problems with a fresh install.

Good luck.

As a counterpart to the BULK INSERT idea, I would think you might also be able to do your stored procedure idea and call "BCP.. IN" from xp_cmdshell within the stored procedure.

Those trace flags writing deadlock info to the errorlog is the only thing I have used as well.

The deadlock information is easy to pick out of the errorlog.. I know...