You can use Import-Export Wizard, I think...

Or maybe export to a Flat File...and then import back on the customer's side...

There is no direct way to do this ...

however you can build a custom solution as shown here:

http://weblogs.sqlteam.com/derekc/archive/2008/01/28/60469.aspx

I do not think Win 7 or Vista are compatible with SQL 2000.

You can refer to the OS requirements below:

http://msdn.microsoft.com/en-us/library/aa176565(v=sql.80).aspx

you can refer http://msdn.microsoft.com/en-us/library/ms175905.aspx for moving existing indexes to other filegroups..

can you tell us what is the relation between the rows...any constraints or is each row just a random combination?

you can decide as to whether you want to focus on Development in SQL Server or move to some parts of Administration...

In development itself, you can get yourself acquainted with...

I also think it maybe more to do with the TempDB not able to extend....as you have mentioned that a lot of temp tables are used..

and max size of the...

This is a very generic error...mainly check the name of the SQL Server instance for any name errors (type, spelling)...

also check if the instance is actually started...these check may seem...

TO find memory usage

select object_name,counter_name, cntr_value 'Memory Used Size (KB)'

FROM

Sys.dm_os_performance_counters

where object_name like '%SQLServer:Memory Manager%'

also you can add the same performance counters in PERFMON

also, i have a smal suggestion...instead of...

Here is a solution for this.

This failure often is caused by a system or domain policy removing the SeDebugPrivelege security privilege from the administrator account running setup. Verify that the...