you need to restore the backup into a separate database and move the tables from filegroup 2 and 3 to Filegroup 1

Then drop filegroups 2 and 3

Cheers,

In addition @command1 expects a varchar the correct way is :

EXEC dbo.sp_MSforeachtable @command1 = 'UPDATE STATISTICS [?] WITH FULLSCAN, ALL'

by the way I have SP4 and have no issues with...

the implication is that more buffer space is needed to cover for the large values. If you are not short in memory this should not be an issue.

I have...

to make compatible behaviours in terms of "metadata" you need to execute:

GRANT VIEW ANY DEFINITION to xxx

GRANT VIEW SERVER STATE to xxx

In terms of security it safer to make someone...

yes. you can simply use:

sp_configure 'max text repl size', 2147483647

how are you changing the database owner ?

you can use partitioned views ( it is not the same but it may serve your purpose )

One of the things I have come across is that *not* prefixing or suffixing tables AND views may save the day on databases with large tables.

You maybe wondering "why?"....

can you ping one from the other ?

The work place makes a *BIG* difference. I have been extremelly lucky to work for very good companies but I have seen the bad ones too. IT is a tough...

I have to say that like colin this sort of operations are to be considered *very* well before you jump the gun. High Performance DB don't take this sort of...

This is overpriced and therefore I would just stay away. You can probably find cheaper alternatives.

Nested transactions are complex and "dangerous". There is a raw limit of 32 on the maximum nested level (on both SQL Server 2000 and 2005) which you can hit if...

your compiled plan is "wrong". Try use with recomplie or parameter sniffing to bypass the issue.

Cheers,

There are *statement* level permissions and *object* level permissions. Truncate table requires the former and therefore can't be bypassed. If this is a recurrent task you could create a job...