Assuming your database isn't in Simple Recovery Mode, you might have a very big Transaction Log with all the data changes in it from the time of the last back up.
If this case you can restore from your full backup and then do a transaction log resotre with the "stop at" attribute (do a search on line)
If you don't, you are up the creek.. and the next part is a very good piece of advice for future habits (other than simply doing backups-and even then it will save you from this sort of problem)
If you are playing with statements that can change data and want to be able to recover (and you probably are tooooo farrr gone at this point) it is a good idea to start every update with a "Begin Tran" and no matching "commit"...
That way if you don't like what you did (and you don't have backups) you can always issue a "rollback".
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.