Start with this web site:

http://www.microsoft.com/sql/evaluation/overview/default.asp

then go here:

http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.asp

-SQLBill

You have two options now:

The one you state. Except then if you need to do a restore, you'll be doing it from the latest full backup (which doesn't have any...

You need to do your deletes in smaller batches. Here's some information about it and a script....

First - gotta give credit where credit is due.

This explaination and script are from...

I would do it as two integers. With varchar you might have to convert it to use math functions.

-SQLBill

Here goes a 'stab in the dark'....

I think I missed an important part of your thread that might have part of the solution.

You say you were updating to Win2K SP4....

1. Do a full backup and then backup the transaction log.

2. Truncate the transaction log.

3. Shrink the transaction log.

None of the above will affect the actual data file of the...

At this point I believe your only option is a call to Microsoft.

It's kinda late for this, but the experience you are going through is why I always stop...

Did you DETACH the database first? This is required for an ATTACH to work.

What do you mean you did 'cut and paste'. Do you mean you MOVED the data files...

Partial restore means that if you have transaction log backups, you can RESTORE to a point-in-time. Let's say your database failed/was corrupted at 12:00. You can do a RESTORE using...

quote:

---

exec sp_attach_single_file_db @dbname = 'eVision_Data', @physname = 'E:\MSSQL7\DATA\eVision_Data.MDF'

---

Are you sure that's the complete path? It's...

I just had this happen. One thing you can try is DETACH the suspect database and then ATTACH it.

I had a restart of my computer that didn't work right and...

Suggestion:

Click on Community, click on Contribution Center and contribute your code. This way it will be placed in the Script list (go to Home and scroll down for a list...

To do what Steve suggests...

Rename and move the .log file

In Enterprise Manager,

Click on Databases, select Attach Database. Browse to the proper .mdf file and select that. Continue with the wizard.

In...

easiest way is to stop and restart SQL Server services.

-SQLBill

BTW-just a minor observation...the subject line says QOD 10/10/2003. Should be 09/10/2003 (it's only September).

-SQLBill