Made me chuckle. Thanks for sharing.

Yeah, got that (it's the online version of the BOL article I mentioned). Unfortunately there's no real easy way to convert that into a script. Besides, even that...

Heh - just realized. "had" is a noise word. Full-text won't work on that one unless you remove it from the file (assuming that you are using the...

Take a look at:

sys.dm_fts_population_ranges

sp_help_fulltext_tables

FULLTEXTCATALOGPROPERTY ('catalog_name' ,'PopulateStatus')

--Also MergeStatus and ItemCount

Being willing to do unanticipated activities outside of my "job description" is what led me to where I am today. If I hadn't been willing to pitch in and...

Well first of all you should really figure out *why* it's in norecovery.

Second, look at the command I gave you. There's no ".bak" file mentioned nor needed.

There's a couple in the scripts here already. Just do a search. I took one and modified it to be what I needed.

Have a look at this article:

http://www.sqlteam.com/article/using-ddl-triggers-in-sql-server-2005-to-capture-schema-changes

Also, do a search here on DDL and trigger

Assuming no active mirroring or replication jobs and assuming I understand your question, I believe issuing:

RESTORE DATABASE MyNwind WITH RECOVERY

GO

should do it. (Replacing MyNwind with the name of your...

It's called "orphaned users".

To find:

EXEC sp_change_users_login 'Report'

To fix:

EXEC sp_change_users_login 'Auto_Fix', 'Chris', NULL, 'pw'

Well, I can see where that would be an issue.

Any idea how the compat level got set to 70?

Can you see the databases in object explorer? Have you looked for orphaned users?

EXEC sp_change_users_login 'Report' --to check for orphaned users

Run Microsoft's Upgrade Adviser (including a check of SQL running on the machine from a profiler trace).

Yup. But verification of status / file location / etc. is the first step.

Regarding the backup / restore note that there is also a command to backup and/or restore...

In SQL Server 2000 full text catalogs are indeed not backed up. However, information about the file location, tables and indexes remain in the database.

With SQL Server 2005, full-text...