Not on a committed transaction. Do you have a backup? If so then it is possible to restore the database with another name and then take the data from the needed table...
Probably not of much help to you now, but usually when I have to make updates to critical production tables, I do something like shown below. First I will execute only the parts shown in green. Then quickly look over the number of rows affected to make sure that it is what I expect it to be, and then run the code in red.
On critical production tables, it has to be done quickly because between the two executions you are keeping the tables locked (or at the very least the rows affected)
BEGIN TRAN
UPDATE MyMostImportantTable SET userId = 0;
ROLLBACK
COMMIT
I have that ROLLBACK in between because if I accidentally execute the code, no harm would be done.
Not on a committed transaction. Do you have a backup? If so then it is possible to restore the database with another name and then take the data from the needed table...
Too old to Rock'n'Roll too young to die.
Thank you for your message. How would I take data from just one table?
Not on a committed transaction. Do you have a backup? If so then it is possible to restore the database with another name and then take the data from the needed table...
Too old to Rock'n'Roll too young to die.
Thank you for your message. How would I take data from just one table?
Thanks.
That was my point. restore the database with another name and then take the data from the needed table
Maybe "another name" isn't clear/bad english? What I meant was "a different name".
Not on a committed transaction. Do you have a backup? If so then it is possible to restore the database with another name and then take the data from the needed table...
Too old to Rock'n'Roll too young to die.
Thank you for your message. How would I take data from just one table?
Thanks.
That was my point. restore the database with another name and then take the data from the needed table
Maybe "another name" isn't clear/bad english? What I meant was "a different name".
Too old to Rock'n'Roll too young to die.
Thank you for your response.
I have tried creating a new database using another name and then restoring the backup of the database that has the problem to the one I have newly created. However, SQL server tells me that it cannot do it because the nf file cannot be overwritten.
Is there another method I could use? Sorry, I am fairly new to SQL server.
Cancel an SQL command
Posted - 10/08/2012 : 06:16:27
