Could you switch the recovery model to simple or bulk-logged when these loads run, then take a full backup after? this will help manage the growth in the log.

You might want to consider taking backup more frequently.

this will reduce the number of VLF's as the space gets freed more frequently. So the file does not need to grow...

I can think of two main reasons for log shipping:

1. Disaster Recovery - you can hold a copy of your database on a different site with log shipping.

I think with...

This link may help in setting the max memeory usage of SQL Server

http://support.microsoft.com/kb/321363

Hey Pete,

You can try the process described in this URL

http://msdn2.microsoft.com/en-us/library/ms188424.aspx

After stopping and restarting the SQL Service If the db is still marked as suspect a restore maybe in...

You can also do this through management studio. database properties--> Options.

Does the db user match the sever login?

Can you grant the db user the datareader role in the database?

I beleieve not 100% sure that deattching and re-attching a database on the same server but moving the file locations, will not reults in orphaned db users...The logins will still...

Hi Danny, depends on your system but it can be goodpractice to put tempdb on a seperate RAID Configuration of its own and the other system databases on a different...

For availability you may want to look at Mirroring or Clustering or log shipping. Various articles are available on the web.

SQLIO allows you to stress test your storage. It would be a good idea to try this before migration so you can iron out any issues with the hardware setup.

I've never moved data to this platform...but I would imagine that SSIS would offer at least some of the functionality that you need.

Check out the SQL Server 2000 Operations Guide. It details the type of information that you should be documenting, basic stuff, but it is important. Store it in a "run...

may sound simple but try and identify what is casuing the growth of tempdb

The account the runs the agent is not the same as the account that runs the sql service... It seems that the account that runs the agent does not have...