[dba-SQLServer] What happens when

Your system tray should have an icon that looks vaguely like a server with a green arrow indicating that it's running. Double-click that and see if you the SQL dialog appears. If not, then I think you have no choice but either to reboot or kill the process itself and start over.

Given the size of the databases you're working with, Oracle might be a better choice since it offers tablespaces (which allow you to partitition a table and place chunks on various drives and servers). But perhaps you can't go there. I sure wish MS-SQL offered that feature. The last gig I worked on had 8 databases and the growth rate was expected to be a TB per year. Oracle would have let us do it all in one DB, with tablespaces pointing to the 8 servers, but since it was an Accenture gig, MS-SQL was the DB. Good thing too, since my Oracle skills are substantially behind my MS skills.

Anyway, there should be no need to run the process you are talking about. Just mark the column(s) PK and that's that. SQL will build the index automatically. You could in theory create a new index containing the same key(s), but what for? What's wrong with the one SQL creates for you?

Arthur

----- Original Message ----
From: JWColby <jwcolby at colbyconsulting.com>
To: dba-sqlserver at databaseadvisors.com
Sent: Tuesday, September 19, 2006 8:31:55 AM
Subject: [dba-SQLServer] What happens when

I am running a process to build an indexedPK on a table.  The database was
set to bulk logged because I was doing massive data imports and forgot to
switch back.  Sigh.  The data file ran out of room.  Double sigh.  EM is
locked up tight.  Is this just going to sit there forever, or is there a
graceful way to say "stop it and let me have control again"?