A recovery model is essentially what you're going to do with the transaction log data. In order to begin working on backups, the business needs define a recovery model. After reading this, you should be able to set up a reasonable set of backups for your system. At best, I'm going to scratch the surface and give you enough information so you won't start crying again. While this article is focused on 2005 syntax, most of the concepts are applicable to 2000. Backups can be created a number of ways and can incorporate all or some of the data, as well as some part of the transaction log. Microsoft, in the SQL Server Books Online defines backups as "a copy of data that is used to restore and recover data after a system failure" which is pretty much what we're looking for. There are things you can do to protect the data under your care and one of the most important is running regular backups of that data. That's right the entire business is in your capable hands, running on that server that doesn't ever crash, with all those end users that don't ever make mistakes using applications built by those developers who right faultless code every time the first time, not to mention the able assistance of that new co-op that has 'sa' privileges thanks to your boss. In the opening chapter of Craig Mullin's book, Database Administration, he says "In many ways, business today is data." The role within most organizations responsible for protecting data is the database administrator… you.
0 Comments
Leave a Reply. |