It looks the the restore of a file to a newer version of SQL Server. Is this a 7.0 file being restored to SQL Server 2000?

David

Sounds like a job for updlock.....(note the super hero undertones - mighty dog generation anyone....)

From BOL...

UPDLOCK Use update locks instead of shared locks while reading a table, and hold locks...

This is a link to an MS msi clean utility that may help. It doesn't list the MSDE product as one of the covered installs but, I believe that is...

Try this in a SQL Job;

xp_cmdshell '\\yourserver\drive:\path\test.bat'

You may even want to build in (either in your .bat file or in SQL) a little rename script so that you can keep...

I part time in many things but 75% of time is MS DB servers (5 SQL 2K, 10 SQL 7.0 and 2 SQL 6.5) that host a myriad of applications...

Neil or anyone,

Can you tell me more about "Note: The problem is not the same as the problem with multiple emails in an operator causing SQL agent to stop"?

I have...

Well it definitely sounds as if the .mdf has problems but it is certainly odd that it did not report similarly when attaching to the server. Hmmm. Anyone else?

David

Did you have multiple log files?

David

My bad, I assumed that the database already existed and that the files were detached. So, being that you are going to create a "new" database with just an .mdf...

Use the single file attach stored proc and you should be good to go!

EXEC sp_attach_single_file_db @dbname = 'pubs',

@physname = 'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf'

David

Andy - Good laugh!!!

However, I am sure that this fine gentlemen is looking for undocumented stored procedures which there are several articles on this site to cover most of...

Dan,

Here are a couple of MS Sites to get you started. The Books On Line is a download that is a great tool and place to gain knowledge of the...

My guess is that this is a shared Access Database which then requires all ODBC DSN Names to be the same as well as connection properties for the linked tables....

Check out this article http://www.sqlservercentral.com/columnists/nboyle/fixingbrokenlogins.asp

I have found this to answer most of these problems.

David

Did you try the copy database wizard that Andy recommended.

Expand the server in Enterprise Manager, right click on the Databases folder, select All Tasks, Copy Database Wizard.

This will...