gosh. If you have data in a database, it must be important. One of the chief requests for help on this and other forums is to recover the contents of a table that someone accidently truncated, deleted, or dropped and the poster doesn't have backups Unless the database is an archive database that's only update once per month or a "staging" database where the data is only transient at best, I'd make sure that the database was set to the FULL Recovery Model and I'd setup Point-in-Time log backups to occur at least once an hour (10 to 15 minutes is my normal setup, though).
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs