Rule "Long path names to files on SQL Server installation media" failed.

SQL Server installation media on a network share or in a custom folder can cause installation failure if the total length of the path exceeds 260 characters. To correct this issue, utilize Net Use functionality or shorten the path name to the SQL Server setup.exe file.

So, I moved it to a shorter path and it installed just fine.

Protecting:
Server 2003 SP2 x64
SQL 2005 SP3

I have about 30 databases being backed up from the one client machine.  All of them backup just fine except one.  Every time I try to do a synchronization or a full backup I get the following error:

Triggering synchronization on *myserver\mydatabase* failed: Error 46: DPM failed to perform the operation because too many objects have been selected. Select fewer objects and then retry this operation.

Error details: The stub received bad data (0x800706F7)

Recommended action: Select fewer objects. 1) If you are trying to protect a large number of data sources on a volume, consider protecting the whole volume instead of individual data sources. 2)If you are trying to recover a large number of folders or files from a volume, consider recovering the parent folder, or divide the recovery into multiple operations.

This happens even if I just select the one database.  All the other databases backup correctly.

After posting in the news group, I got a question from a Microsoft person whether full text indexing was enabled, and if so how many catalogs.  Upon investigation, it appears that this is one of the only databases that i have that has full text indexing enabled.  It has 32 indexes. 

So with the suggestion of a colleague, I did a rebuild of the indexes:

1. In SQL Server Management Studio (SSMS) expand the database/Storage/Full Text Catalogs
2. Right click on the Full Text Catalogs folder and select Rebuild All

Then I went back to my DPM server, to the protection group and selected the database in question.  I did a “Create recovery point – Disk”, “Create a recovery point by using express full backup”.

That worked, so maybe that means the problem is fixed…

Anyway, I was looking for a quick way to copy a table from one Database to another and came across this blog which I think has a lot of good queries just waiting to be tinkered with:

http://www.sqlservercurry.com/

And the particular post that got me there was:

Copy a table from one database to another in SQL Server 2005

4:09 AM Posted by Suprotim Agarwal
Labels: SQL Server Administration

If you have a table in a database and you would like to copy the table to another database, use this query:
SELECT * INTO AdventureWorks.dbo.CustomersTemp FROM Northwind.dbo.Customers
Just remember that using this query will only transfer the schema and data. It does not transfer the indexes, foreign keys, statistics etc.
If you want to transfer all the objects from one database to another, open Sql Server Management Studio > Right click on your database > All Tasks > Generate SQL Scripts. Then run these scripts against the new database.
Transfer both schema and data
To copy both data and schema, use the Microsoft SQL Server Database Publishing Wizard 1.1. This tool works for both SQL 2000 and SQL 2005 and generates a single SQL script file which can be used to recreate a database (both schema and data).