It's been a while since my last (and only) post. I am in transition from the position I had to another position with the same company. My new job is working as part of a team that will upgrade the software for a major International banking company. I get to learn Sybase, it has a SQL Server flavor to it considering Sybase used to have a partnership with Microsoft.
It sounds like my focus will be on upgrading triggers and helping out with database replication. I'm looking forward to doing that and working with the DBA team!
Thursday, May 14, 2009
Wednesday, February 11, 2009
MSSQL 2000 Backups
Well, I just learned something. So instead of an introduction to who I am, how about a quick lesson learned.
I was manually backing up an MSSQL 2000 database because a job that is supposed to do it has been failing.
Anyway, this particular lesson includes backing up a 600+ GB database. The job that runs is scheduled to run in just over an hour. I decided to stop the job after it had been running for about 30 mins because I figured it would run past "job time" and fail. I looked in the directory where the backup had been writing to, and found out that indeed, the backup had been writing.
The job ran for almost half an hour on a disk that had an old copy of the backup, and ~30 GB free. I was kind of shocked that the job hadn't failed by now, and wondered if MSSQL would prep the whole database before it wrote to disk. IT DOESN'T! The backup went from 400+ GB to just under 200GB. Good thing the disk gets backed up every night, although the last successful backup was months ago I can get it if I need to.
Anyway, I think I got things worked out so that the original job will run successfully tonight, and then I will have a brand new backup... of all three databases. We'll see in the morning.
I was manually backing up an MSSQL 2000 database because a job that is supposed to do it has been failing.
Anyway, this particular lesson includes backing up a 600+ GB database. The job that runs is scheduled to run in just over an hour. I decided to stop the job after it had been running for about 30 mins because I figured it would run past "job time" and fail. I looked in the directory where the backup had been writing to, and found out that indeed, the backup had been writing.
The job ran for almost half an hour on a disk that had an old copy of the backup, and ~30 GB free. I was kind of shocked that the job hadn't failed by now, and wondered if MSSQL would prep the whole database before it wrote to disk. IT DOESN'T! The backup went from 400+ GB to just under 200GB. Good thing the disk gets backed up every night, although the last successful backup was months ago I can get it if I need to.
Anyway, I think I got things worked out so that the original job will run successfully tonight, and then I will have a brand new backup... of all three databases. We'll see in the morning.
Subscribe to:
Posts (Atom)