"Full" database access is open to interpretation, so I guess you'll have to define it. I generally figure a database user i.e. a customer needs to read, update, insert,...

You won't hurt anything by deleting the old error log file and that's the only way to get rid of it.

If you have the space and you don't care if you have a named instance, you should leave the SQL 2000 instance and install SQL 2005 as a named instance....

See my first response for how to add a job step for executing a package. You didn't specify what your scripts do, but generally you can just put them...

Mike,

I haven't seen that problem myself, but does this help?

http://forums.microsoft.com/msdn/showpost.aspx?postid=75967&siteid=1

I side with the second person. Insert batch size is the number of successful insertions between commits, so if it's set to 10,000, it will commit a transaction every...

Did you save the package to SQL Server or as a file? Connect to Integration Services on the server where you saved the package and look in Stored Packages...

Use a script with ALTER LOGIN loginname DISABLE for each login and another script with ALTER LOGIN loginname ENABLE for each login. This works for both SQL Server logins...

Your stop job should only have sp_trace_setstatus in it, not the sp_trace_create part. If you run that again it's like you're trying to create the same trace again.

Looks right to me. BTW, the 2 option is sp_trace_create specifies that a new trace file will be created when the current file reaches it's max file size (which...

You only need to create the trace once.

Once you create the trace, put sp_trace_setstatus trace_id, 1 in a job sceduled to run at 11:00 PM and put sp_trace_setstatus trace_id, 0...

The trace file name is nvarchar(245). Did you specify N'D:\test\test1.trc? You can set the stop time using the @stoptime parameter of sp_trace_create or you can use sp_trace_setstatus to...

Logins don't move with a database so you'd either have to create them or transfer them seperately.

http://support.microsoft.com/kb/918992/en-us

There is an SSIS task called the Transfer Logins Task. BOL has instructions...

I found this in the script section, but I haven't used it.

http://www.sqlservercentral.com/scripts/Miscellaneous/31613/

You can start a trace without using the Profiler GUI. See my replies in this thread describing how to create, start and stop a server-side trace: http://www.sqlservercentral.com/Forums/Topic529790-5-1.aspx