Check this website that will tell you what to do:

http://weblogs.sqlteam.com/randyp/archive/2009/03/04/60863.aspx

1. The default option for the filegroup only sets the option that any data inserted from that point on will be written in that filegroup. SQL Server "sees" the data...

The problem is not in the EXEC method but in the configuration of the liked server. How did you configure the linked server in the "Security" section?

Do you impersonate a...

If you want to use filegroups I would adviose you to also look at partitioning your tables and indexes because that can improve your performance dramatically.

Look at this article to...

It depends, what is your security policy in your company.

If your manager wants to know every change in the database than you can implement the logging for changes. If you...

This article is meant for SQL 2005 in a clustered environment. You probably don't need do these steps when you have a non-clustered environment. I haven't tested the method voor...

If you have a very active database you can certainly benefit from the fact that you have more filegroups.

You're correct about the points you wrote in your post. Another advantage...

You can try to rebuild your master db. In this tutorial you can see the steps how to do that:

http://geekswithblogs.net/mskoolaid/archive/2005/12/17/63413.aspx

Don't mind the fact that they talk about Windows...

No you can't. You could try to script your database to import it into SQL 2000.

Try this article to do this: http://www.sql-articles.com/index.php?page=articles/migrating_2005_2000.html

It could be that it is hardware related. I've had several people with the same problem but others that didn't have the problem.

When I get execute the jobs I get the following error by starting the powershell script:

Exception calling "WriteToServer" with "1" argument(s): "Violation of PRIMARY K EY constraint 'PK_backupset_dim'. Cannot...