Table a database offline;

Copy the database files to your target server;

Attach the copied files on the target server.

Index should not be changed. Dropping indexes before truncating a table is for breaking relations between tables.

As David stated, applying SP4 may fix your problem. Here is a link, which may be helpful to you.

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

Remember, view is a virtual table, not a real one. You need to put data into a real table.

Did you read this article posted about 2 years ago?

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=169&messageid=247574

You may try to set max memory for SQL Server under the Memory tab in the SQL Server Properties dialog.

It is hard for me to understand your question. My guess is:

SELECT veh.*, config.* FROM veh, config WHERE veh.make = config.make

Based on the following link, the error may come from inserts.

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

It is hard to explain why your system works for about one week after rebooting, unless your data...

Are you the administrator on the SAN drive? Is there any contraint (allocation size) to your account ?

You can export SQL Server data into excel file without using stored procedures.

No question is stupid.

Based on my understanding, the error (DB-Library) you mentioned came from a "procedure" built-in SQL Server (internal SQL Server procedure).

Using the SQL profiler may trace some...

Did you try to import the data in master..sysservers from your source server?

My input:

Adding indexes may increase the size of a database tremendously, in particular, for a huge table with about 30 indexes. It will not surprise me if you tell...

The number of pages may not be a good parameter for planning a disk capacity. I would like to use the data of used space instead.

The backup device is used with other 2 devices. Backup data are evenly split into these devices (members). To find the members, you can choose Properties by right-clicking device icons. Then,...