Yes I think it came in for 2005.

http://msdn.microsoft.com/en-us/library/ms345146(SQL.90).aspx

I'd consider the ability to use SWITCH for archiving large amounts of data from one partitioned table to another a great benefit when only having one disk. The IO saved...

No problem. We all start somewhere. 🙂

Something like

Select ID, count(*)

from table

group by ID

having count(*) = 1

Depends on what you're doing. Yes, the isolation level set is just for that session / connection until you specify otherwise, it does not have an affect on other queries...

No, the READ UNCOMMITTED is used so the query doesn't have an impact. It doesn't care about locks and places none of its own

Do your backup before, not during.

Also, simply placing the DB in BULK-LOGGED mode won't guarantee minimal logging. There are some cases where full logging will still occur, even when the...

If you do a

select * from sys.filegroups

can you see the [TERTIARY] filegroup?

*OK ignore, I wasn't quick enough. Lowell has given you the solution. 🙂

Your best bet is to have the DB in FULL mode for normal operations, then switch to BULK-LOGGED when you need to do the import. Then switch back to FULL...

You should create a script to cycle through a list of the databases you need to restore. Would be quicker / easier than doing them all manually.

Can you post the SQL you're using to create the table

Good points made in the article linked there. I assumed the extra records were uncommitted transactions and hadn't considered page splits etc when using nolock / read uncommitted leading to...

Do you backup the transaction log? If so, can your restore to point in time just prior to event? If not, then i'd argue it must be because a certain...

If you're just needing to get a copy of the databases in their current state onto another server, and are not too concerned with applying new transactions etc, then why...

Check out the dbname field from the sys.syslogins. This is the default database per login.