Just wondering what some of the backup strategies are out there. Full
backups, log backups, filegroup backups? What are the sizes of your
databases?
Thanks just looking for some insight on what other people are doing with
large data warehouse databases.
Have a good day,
Jim
FYI
we use different strategies depending on the function of the database, eg
for our datawarehouse (approx 120 GB) I use the simple model, with online
backup of the db every night (takes 1,5 hours), before the nightjobs run. We
can always re-run the nightjobs from a give point in time so this scheme
will do.
For high availability production databases, I do log backups every 60
minutes, and a night backup of the db's. That way, the loss of data should
be maximum 60 minutes should we need to restore the database after a fatal
crash. Alse, the frequent backup of the logs keeps their size relatively
small (up to about 5 GB), backup of logs is first to disk for speed, then to
tape for safety.
Hope this is of some use to you...
"JimW" <JimW@.discussions.microsoft.com> schreef in bericht
news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
> Just wondering what some of the backup strategies are out there. Full
> backups, log backups, filegroup backups? What are the sizes of your
> databases?
> Thanks just looking for some insight on what other people are doing with
> large data warehouse databases.
> --
> Have a good day,
> Jim
|||might be worth looking at SQLLitespeed if you have large backups
http://www.imceda.com/
Andy
"JimW" <JimW@.discussions.microsoft.com> wrote in message
news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
> Just wondering what some of the backup strategies are out there. Full
> backups, log backups, filegroup backups? What are the sizes of your
> databases?
> Thanks just looking for some insight on what other people are doing with
> large data warehouse databases.
> --
> Have a good day,
> Jim
|||Just wondering, why backup the datawarehouse? Normally the data come from
other sources anyway, so it should be suficient to backup the production
db's. Now, what I do is I transfer, without data all the object to a backup
database and backup this every night so that I maintain the structure only.
That saves about 50% of the space.
T
"admin" <admin@.wol.be> escreveu na mensagem
news:412f713f$0$321$ba620e4c@.news.skynet.be...
> FYI
> we use different strategies depending on the function of the database, eg
> for our datawarehouse (approx 120 GB) I use the simple model, with online
> backup of the db every night (takes 1,5 hours), before the nightjobs run.
We
> can always re-run the nightjobs from a give point in time so this scheme
> will do.
> For high availability production databases, I do log backups every 60
> minutes, and a night backup of the db's. That way, the loss of data should
> be maximum 60 minutes should we need to restore the database after a fatal
> crash. Alse, the frequent backup of the logs keeps their size relatively
> small (up to about 5 GB), backup of logs is first to disk for speed, then
to
> tape for safety.
> Hope this is of some use to you...
>
> "JimW" <JimW@.discussions.microsoft.com> schreef in bericht
> news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
>
Showing posts with label sizes. Show all posts
Showing posts with label sizes. Show all posts
Thursday, March 29, 2012
Backup Strategies
Just wondering what some of the backup strategies are out there. Full
backups, log backups, filegroup backups? What are the sizes of your
databases?
Thanks just looking for some insight on what other people are doing with
large data warehouse databases.
--
Have a good day,
JimFYI
we use different strategies depending on the function of the database, eg
for our datawarehouse (approx 120 GB) I use the simple model, with online
backup of the db every night (takes 1,5 hours), before the nightjobs run. We
can always re-run the nightjobs from a give point in time so this scheme
will do.
For high availability production databases, I do log backups every 60
minutes, and a night backup of the db's. That way, the loss of data should
be maximum 60 minutes should we need to restore the database after a fatal
crash. Alse, the frequent backup of the logs keeps their size relatively
small (up to about 5 GB), backup of logs is first to disk for speed, then to
tape for safety.
Hope this is of some use to you...
"JimW" <JimW@.discussions.microsoft.com> schreef in bericht
news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
> Just wondering what some of the backup strategies are out there. Full
> backups, log backups, filegroup backups? What are the sizes of your
> databases?
> Thanks just looking for some insight on what other people are doing with
> large data warehouse databases.
> --
> Have a good day,
> Jim|||might be worth looking at SQLLitespeed if you have large backups
http://www.imceda.com/
Andy
"JimW" <JimW@.discussions.microsoft.com> wrote in message
news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
> Just wondering what some of the backup strategies are out there. Full
> backups, log backups, filegroup backups? What are the sizes of your
> databases?
> Thanks just looking for some insight on what other people are doing with
> large data warehouse databases.
> --
> Have a good day,
> Jim|||Just wondering, why backup the datawarehouse? Normally the data come from
other sources anyway, so it should be suficient to backup the production
db's. Now, what I do is I transfer, without data all the object to a backup
database and backup this every night so that I maintain the structure only.
That saves about 50% of the space.
T
"admin" <admin@.wol.be> escreveu na mensagem
news:412f713f$0$321$ba620e4c@.news.skynet.be...
> FYI
> we use different strategies depending on the function of the database, eg
> for our datawarehouse (approx 120 GB) I use the simple model, with online
> backup of the db every night (takes 1,5 hours), before the nightjobs run.
We
> can always re-run the nightjobs from a give point in time so this scheme
> will do.
> For high availability production databases, I do log backups every 60
> minutes, and a night backup of the db's. That way, the loss of data should
> be maximum 60 minutes should we need to restore the database after a fatal
> crash. Alse, the frequent backup of the logs keeps their size relatively
> small (up to about 5 GB), backup of logs is first to disk for speed, then
to
> tape for safety.
> Hope this is of some use to you...
>
> "JimW" <JimW@.discussions.microsoft.com> schreef in bericht
> news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
>
backups, log backups, filegroup backups? What are the sizes of your
databases?
Thanks just looking for some insight on what other people are doing with
large data warehouse databases.
--
Have a good day,
JimFYI
we use different strategies depending on the function of the database, eg
for our datawarehouse (approx 120 GB) I use the simple model, with online
backup of the db every night (takes 1,5 hours), before the nightjobs run. We
can always re-run the nightjobs from a give point in time so this scheme
will do.
For high availability production databases, I do log backups every 60
minutes, and a night backup of the db's. That way, the loss of data should
be maximum 60 minutes should we need to restore the database after a fatal
crash. Alse, the frequent backup of the logs keeps their size relatively
small (up to about 5 GB), backup of logs is first to disk for speed, then to
tape for safety.
Hope this is of some use to you...
"JimW" <JimW@.discussions.microsoft.com> schreef in bericht
news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
> Just wondering what some of the backup strategies are out there. Full
> backups, log backups, filegroup backups? What are the sizes of your
> databases?
> Thanks just looking for some insight on what other people are doing with
> large data warehouse databases.
> --
> Have a good day,
> Jim|||might be worth looking at SQLLitespeed if you have large backups
http://www.imceda.com/
Andy
"JimW" <JimW@.discussions.microsoft.com> wrote in message
news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
> Just wondering what some of the backup strategies are out there. Full
> backups, log backups, filegroup backups? What are the sizes of your
> databases?
> Thanks just looking for some insight on what other people are doing with
> large data warehouse databases.
> --
> Have a good day,
> Jim|||Just wondering, why backup the datawarehouse? Normally the data come from
other sources anyway, so it should be suficient to backup the production
db's. Now, what I do is I transfer, without data all the object to a backup
database and backup this every night so that I maintain the structure only.
That saves about 50% of the space.
T
"admin" <admin@.wol.be> escreveu na mensagem
news:412f713f$0$321$ba620e4c@.news.skynet.be...
> FYI
> we use different strategies depending on the function of the database, eg
> for our datawarehouse (approx 120 GB) I use the simple model, with online
> backup of the db every night (takes 1,5 hours), before the nightjobs run.
We
> can always re-run the nightjobs from a give point in time so this scheme
> will do.
> For high availability production databases, I do log backups every 60
> minutes, and a night backup of the db's. That way, the loss of data should
> be maximum 60 minutes should we need to restore the database after a fatal
> crash. Alse, the frequent backup of the logs keeps their size relatively
> small (up to about 5 GB), backup of logs is first to disk for speed, then
to
> tape for safety.
> Hope this is of some use to you...
>
> "JimW" <JimW@.discussions.microsoft.com> schreef in bericht
> news:1B4D84BE-5D56-40E1-BFED-859C829F5C01@.microsoft.com...
>
Sunday, March 25, 2012
Backup sizes?
I have a maintenance plan set up so that we do a full backup every Sunday
night. We then do a differential backup every night at 11:00. Additionally we
do transaction log backups every hour from 5:00 in the morning until 9:00 at
night. I recently noticed that my differential backup was about 7 times the
size of my full backup. Does this make sense to anyone else? What could be
causing this? Thanks. MattHi
Are you appending the backup into a single file?
It is best to give every backup a new file, every time it is run.
Regards
Mike
"Matt" wrote:
> I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally we
> do transaction log backups every hour from 5:00 in the morning until 9:00 at
> night. I recently noticed that my differential backup was about 7 times the
> size of my full backup. Does this make sense to anyone else? What could be
> causing this? Thanks. Matt|||You need to specify the WITH INIT option otherwise it appends each backup to
the prior one. Why not simply do a FULL backup once a night?
--
Andrew J. Kelly SQL MVP
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally
> we
> do transaction log backups every hour from 5:00 in the morning until 9:00
> at
> night. I recently noticed that my differential backup was about 7 times
> the
> size of my full backup. Does this make sense to anyone else? What could
> be
> causing this? Thanks. Matt|||Would it not be faster to restore with my current setup? If not, then I
probably will just go to a Full backup every night. Thanks.
"Andrew J. Kelly" wrote:
> You need to specify the WITH INIT option otherwise it appends each backup to
> the prior one. Why not simply do a FULL backup once a night?
> --
> Andrew J. Kelly SQL MVP
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
> >I have a maintenance plan set up so that we do a full backup every Sunday
> > night. We then do a differential backup every night at 11:00. Additionally
> > we
> > do transaction log backups every hour from 5:00 in the morning until 9:00
> > at
> > night. I recently noticed that my differential backup was about 7 times
> > the
> > size of my full backup. Does this make sense to anyone else? What could
> > be
> > causing this? Thanks. Matt
>
>|||> Would it not be faster to restore with my current setup?
Au contraire. With your current setup, you have to first restore the latest database backup, then
the latest diff backup, then all subsequent log backups.
With Andrew's suggestion you just restore the latest database backup and then all subsequent log
backup (same number of log backups as above scenario).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
> Would it not be faster to restore with my current setup? If not, then I
> probably will just go to a Full backup every night. Thanks.
> "Andrew J. Kelly" wrote:
>> You need to specify the WITH INIT option otherwise it appends each backup to
>> the prior one. Why not simply do a FULL backup once a night?
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Matt" <Matt@.discussions.microsoft.com> wrote in message
>> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>> >I have a maintenance plan set up so that we do a full backup every Sunday
>> > night. We then do a differential backup every night at 11:00. Additionally
>> > we
>> > do transaction log backups every hour from 5:00 in the morning until 9:00
>> > at
>> > night. I recently noticed that my differential backup was about 7 times
>> > the
>> > size of my full backup. Does this make sense to anyone else? What could
>> > be
>> > causing this? Thanks. Matt
>>|||Thanks to everyone for your help. I assume the only reason to use
differential backups is if you don't have a very big window to do a full
backup? Again, thanks. Matt
"Tibor Karaszi" wrote:
> > Would it not be faster to restore with my current setup?
> Au contraire. With your current setup, you have to first restore the latest database backup, then
> the latest diff backup, then all subsequent log backups.
> With Andrew's suggestion you just restore the latest database backup and then all subsequent log
> backup (same number of log backups as above scenario).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
> > Would it not be faster to restore with my current setup? If not, then I
> > probably will just go to a Full backup every night. Thanks.
> >
> > "Andrew J. Kelly" wrote:
> >
> >> You need to specify the WITH INIT option otherwise it appends each backup to
> >> the prior one. Why not simply do a FULL backup once a night?
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> >> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
> >> >I have a maintenance plan set up so that we do a full backup every Sunday
> >> > night. We then do a differential backup every night at 11:00. Additionally
> >> > we
> >> > do transaction log backups every hour from 5:00 in the morning until 9:00
> >> > at
> >> > night. I recently noticed that my differential backup was about 7 times
> >> > the
> >> > size of my full backup. Does this make sense to anyone else? What could
> >> > be
> >> > causing this? Thanks. Matt
> >>
> >>
> >>
>
>|||> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup?
Yes, something like that. Or disk space prohibits you from doing db backups with that frequency...
:-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:B64881EC-6D15-4AFE-ABBF-47BFF7CBCA79@.microsoft.com...
> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup? Again, thanks. Matt
> "Tibor Karaszi" wrote:
>> > Would it not be faster to restore with my current setup?
>> Au contraire. With your current setup, you have to first restore the latest database backup, then
>> the latest diff backup, then all subsequent log backups.
>> With Andrew's suggestion you just restore the latest database backup and then all subsequent log
>> backup (same number of log backups as above scenario).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "Matt" <Matt@.discussions.microsoft.com> wrote in message
>> news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
>> > Would it not be faster to restore with my current setup? If not, then I
>> > probably will just go to a Full backup every night. Thanks.
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> You need to specify the WITH INIT option otherwise it appends each backup to
>> >> the prior one. Why not simply do a FULL backup once a night?
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Matt" <Matt@.discussions.microsoft.com> wrote in message
>> >> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>> >> >I have a maintenance plan set up so that we do a full backup every Sunday
>> >> > night. We then do a differential backup every night at 11:00. Additionally
>> >> > we
>> >> > do transaction log backups every hour from 5:00 in the morning until 9:00
>> >> > at
>> >> > night. I recently noticed that my differential backup was about 7 times
>> >> > the
>> >> > size of my full backup. Does this make sense to anyone else? What could
>> >> > be
>> >> > causing this? Thanks. Matt
>> >>
>> >>
>> >>
>>
night. We then do a differential backup every night at 11:00. Additionally we
do transaction log backups every hour from 5:00 in the morning until 9:00 at
night. I recently noticed that my differential backup was about 7 times the
size of my full backup. Does this make sense to anyone else? What could be
causing this? Thanks. MattHi
Are you appending the backup into a single file?
It is best to give every backup a new file, every time it is run.
Regards
Mike
"Matt" wrote:
> I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally we
> do transaction log backups every hour from 5:00 in the morning until 9:00 at
> night. I recently noticed that my differential backup was about 7 times the
> size of my full backup. Does this make sense to anyone else? What could be
> causing this? Thanks. Matt|||You need to specify the WITH INIT option otherwise it appends each backup to
the prior one. Why not simply do a FULL backup once a night?
--
Andrew J. Kelly SQL MVP
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally
> we
> do transaction log backups every hour from 5:00 in the morning until 9:00
> at
> night. I recently noticed that my differential backup was about 7 times
> the
> size of my full backup. Does this make sense to anyone else? What could
> be
> causing this? Thanks. Matt|||Would it not be faster to restore with my current setup? If not, then I
probably will just go to a Full backup every night. Thanks.
"Andrew J. Kelly" wrote:
> You need to specify the WITH INIT option otherwise it appends each backup to
> the prior one. Why not simply do a FULL backup once a night?
> --
> Andrew J. Kelly SQL MVP
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
> >I have a maintenance plan set up so that we do a full backup every Sunday
> > night. We then do a differential backup every night at 11:00. Additionally
> > we
> > do transaction log backups every hour from 5:00 in the morning until 9:00
> > at
> > night. I recently noticed that my differential backup was about 7 times
> > the
> > size of my full backup. Does this make sense to anyone else? What could
> > be
> > causing this? Thanks. Matt
>
>|||> Would it not be faster to restore with my current setup?
Au contraire. With your current setup, you have to first restore the latest database backup, then
the latest diff backup, then all subsequent log backups.
With Andrew's suggestion you just restore the latest database backup and then all subsequent log
backup (same number of log backups as above scenario).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
> Would it not be faster to restore with my current setup? If not, then I
> probably will just go to a Full backup every night. Thanks.
> "Andrew J. Kelly" wrote:
>> You need to specify the WITH INIT option otherwise it appends each backup to
>> the prior one. Why not simply do a FULL backup once a night?
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Matt" <Matt@.discussions.microsoft.com> wrote in message
>> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>> >I have a maintenance plan set up so that we do a full backup every Sunday
>> > night. We then do a differential backup every night at 11:00. Additionally
>> > we
>> > do transaction log backups every hour from 5:00 in the morning until 9:00
>> > at
>> > night. I recently noticed that my differential backup was about 7 times
>> > the
>> > size of my full backup. Does this make sense to anyone else? What could
>> > be
>> > causing this? Thanks. Matt
>>|||Thanks to everyone for your help. I assume the only reason to use
differential backups is if you don't have a very big window to do a full
backup? Again, thanks. Matt
"Tibor Karaszi" wrote:
> > Would it not be faster to restore with my current setup?
> Au contraire. With your current setup, you have to first restore the latest database backup, then
> the latest diff backup, then all subsequent log backups.
> With Andrew's suggestion you just restore the latest database backup and then all subsequent log
> backup (same number of log backups as above scenario).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
> > Would it not be faster to restore with my current setup? If not, then I
> > probably will just go to a Full backup every night. Thanks.
> >
> > "Andrew J. Kelly" wrote:
> >
> >> You need to specify the WITH INIT option otherwise it appends each backup to
> >> the prior one. Why not simply do a FULL backup once a night?
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> >> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
> >> >I have a maintenance plan set up so that we do a full backup every Sunday
> >> > night. We then do a differential backup every night at 11:00. Additionally
> >> > we
> >> > do transaction log backups every hour from 5:00 in the morning until 9:00
> >> > at
> >> > night. I recently noticed that my differential backup was about 7 times
> >> > the
> >> > size of my full backup. Does this make sense to anyone else? What could
> >> > be
> >> > causing this? Thanks. Matt
> >>
> >>
> >>
>
>|||> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup?
Yes, something like that. Or disk space prohibits you from doing db backups with that frequency...
:-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:B64881EC-6D15-4AFE-ABBF-47BFF7CBCA79@.microsoft.com...
> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup? Again, thanks. Matt
> "Tibor Karaszi" wrote:
>> > Would it not be faster to restore with my current setup?
>> Au contraire. With your current setup, you have to first restore the latest database backup, then
>> the latest diff backup, then all subsequent log backups.
>> With Andrew's suggestion you just restore the latest database backup and then all subsequent log
>> backup (same number of log backups as above scenario).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "Matt" <Matt@.discussions.microsoft.com> wrote in message
>> news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
>> > Would it not be faster to restore with my current setup? If not, then I
>> > probably will just go to a Full backup every night. Thanks.
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> You need to specify the WITH INIT option otherwise it appends each backup to
>> >> the prior one. Why not simply do a FULL backup once a night?
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "Matt" <Matt@.discussions.microsoft.com> wrote in message
>> >> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>> >> >I have a maintenance plan set up so that we do a full backup every Sunday
>> >> > night. We then do a differential backup every night at 11:00. Additionally
>> >> > we
>> >> > do transaction log backups every hour from 5:00 in the morning until 9:00
>> >> > at
>> >> > night. I recently noticed that my differential backup was about 7 times
>> >> > the
>> >> > size of my full backup. Does this make sense to anyone else? What could
>> >> > be
>> >> > causing this? Thanks. Matt
>> >>
>> >>
>> >>
>>
Backup sizes?
I have a maintenance plan set up so that we do a full backup every Sunday
night. We then do a differential backup every night at 11:00. Additionally w
e
do transaction log backups every hour from 5:00 in the morning until 9:00 at
night. I recently noticed that my differential backup was about 7 times the
size of my full backup. Does this make sense to anyone else? What could be
causing this? Thanks. MattHi
Are you appending the backup into a single file?
It is best to give every backup a new file, every time it is run.
Regards
Mike
"Matt" wrote:
> I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally
we
> do transaction log backups every hour from 5:00 in the morning until 9:00
at
> night. I recently noticed that my differential backup was about 7 times th
e
> size of my full backup. Does this make sense to anyone else? What could b
e
> causing this? Thanks. Matt|||You need to specify the WITH INIT option otherwise it appends each backup to
the prior one. Why not simply do a FULL backup once a night?
Andrew J. Kelly SQL MVP
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally
> we
> do transaction log backups every hour from 5:00 in the morning until 9:00
> at
> night. I recently noticed that my differential backup was about 7 times
> the
> size of my full backup. Does this make sense to anyone else? What could
> be
> causing this? Thanks. Matt|||Would it not be faster to restore with my current setup? If not, then I
probably will just go to a Full backup every night. Thanks.
"Andrew J. Kelly" wrote:
> You need to specify the WITH INIT option otherwise it appends each backup
to
> the prior one. Why not simply do a FULL backup once a night?
> --
> Andrew J. Kelly SQL MVP
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>
>|||> Would it not be faster to restore with my current setup?
Au contraire. With your current setup, you have to first restore the latest
database backup, then
the latest diff backup, then all subsequent log backups.
With Andrew's suggestion you just restore the latest database backup and the
n all subsequent log
backup (same number of log backups as above scenario).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...[vbcol=seagreen]
> Would it not be faster to restore with my current setup? If not, then I
> probably will just go to a Full backup every night. Thanks.
> "Andrew J. Kelly" wrote:
>|||Thanks to everyone for your help. I assume the only reason to use
differential backups is if you don't have a very big window to do a full
backup? Again, thanks. Matt
"Tibor Karaszi" wrote:
> Au contraire. With your current setup, you have to first restore the lates
t database backup, then
> the latest diff backup, then all subsequent log backups.
> With Andrew's suggestion you just restore the latest database backup and t
hen all subsequent log
> backup (same number of log backups as above scenario).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
>
>|||> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup?
Yes, something like that. Or disk space prohibits you from doing db backups
with that frequency...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:B64881EC-6D15-4AFE-ABBF-47BFF7CBCA79@.microsoft.com...[vbcol=seagreen]
> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup? Again, thanks. Matt
> "Tibor Karaszi" wrote:
>sql
night. We then do a differential backup every night at 11:00. Additionally w
e
do transaction log backups every hour from 5:00 in the morning until 9:00 at
night. I recently noticed that my differential backup was about 7 times the
size of my full backup. Does this make sense to anyone else? What could be
causing this? Thanks. MattHi
Are you appending the backup into a single file?
It is best to give every backup a new file, every time it is run.
Regards
Mike
"Matt" wrote:
> I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally
we
> do transaction log backups every hour from 5:00 in the morning until 9:00
at
> night. I recently noticed that my differential backup was about 7 times th
e
> size of my full backup. Does this make sense to anyone else? What could b
e
> causing this? Thanks. Matt|||You need to specify the WITH INIT option otherwise it appends each backup to
the prior one. Why not simply do a FULL backup once a night?
Andrew J. Kelly SQL MVP
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally
> we
> do transaction log backups every hour from 5:00 in the morning until 9:00
> at
> night. I recently noticed that my differential backup was about 7 times
> the
> size of my full backup. Does this make sense to anyone else? What could
> be
> causing this? Thanks. Matt|||Would it not be faster to restore with my current setup? If not, then I
probably will just go to a Full backup every night. Thanks.
"Andrew J. Kelly" wrote:
> You need to specify the WITH INIT option otherwise it appends each backup
to
> the prior one. Why not simply do a FULL backup once a night?
> --
> Andrew J. Kelly SQL MVP
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>
>|||> Would it not be faster to restore with my current setup?
Au contraire. With your current setup, you have to first restore the latest
database backup, then
the latest diff backup, then all subsequent log backups.
With Andrew's suggestion you just restore the latest database backup and the
n all subsequent log
backup (same number of log backups as above scenario).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...[vbcol=seagreen]
> Would it not be faster to restore with my current setup? If not, then I
> probably will just go to a Full backup every night. Thanks.
> "Andrew J. Kelly" wrote:
>|||Thanks to everyone for your help. I assume the only reason to use
differential backups is if you don't have a very big window to do a full
backup? Again, thanks. Matt
"Tibor Karaszi" wrote:
> Au contraire. With your current setup, you have to first restore the lates
t database backup, then
> the latest diff backup, then all subsequent log backups.
> With Andrew's suggestion you just restore the latest database backup and t
hen all subsequent log
> backup (same number of log backups as above scenario).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
>
>|||> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup?
Yes, something like that. Or disk space prohibits you from doing db backups
with that frequency...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:B64881EC-6D15-4AFE-ABBF-47BFF7CBCA79@.microsoft.com...[vbcol=seagreen]
> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup? Again, thanks. Matt
> "Tibor Karaszi" wrote:
>sql
Backup sizes?
I have a maintenance plan set up so that we do a full backup every Sunday
night. We then do a differential backup every night at 11:00. Additionally we
do transaction log backups every hour from 5:00 in the morning until 9:00 at
night. I recently noticed that my differential backup was about 7 times the
size of my full backup. Does this make sense to anyone else? What could be
causing this? Thanks. Matt
Hi
Are you appending the backup into a single file?
It is best to give every backup a new file, every time it is run.
Regards
Mike
"Matt" wrote:
> I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally we
> do transaction log backups every hour from 5:00 in the morning until 9:00 at
> night. I recently noticed that my differential backup was about 7 times the
> size of my full backup. Does this make sense to anyone else? What could be
> causing this? Thanks. Matt
|||You need to specify the WITH INIT option otherwise it appends each backup to
the prior one. Why not simply do a FULL backup once a night?
Andrew J. Kelly SQL MVP
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally
> we
> do transaction log backups every hour from 5:00 in the morning until 9:00
> at
> night. I recently noticed that my differential backup was about 7 times
> the
> size of my full backup. Does this make sense to anyone else? What could
> be
> causing this? Thanks. Matt
|||Would it not be faster to restore with my current setup? If not, then I
probably will just go to a Full backup every night. Thanks.
"Andrew J. Kelly" wrote:
> You need to specify the WITH INIT option otherwise it appends each backup to
> the prior one. Why not simply do a FULL backup once a night?
> --
> Andrew J. Kelly SQL MVP
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>
>
|||> Would it not be faster to restore with my current setup?
Au contraire. With your current setup, you have to first restore the latest database backup, then
the latest diff backup, then all subsequent log backups.
With Andrew's suggestion you just restore the latest database backup and then all subsequent log
backup (same number of log backups as above scenario).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...[vbcol=seagreen]
> Would it not be faster to restore with my current setup? If not, then I
> probably will just go to a Full backup every night. Thanks.
> "Andrew J. Kelly" wrote:
|||Thanks to everyone for your help. I assume the only reason to use
differential backups is if you don't have a very big window to do a full
backup? Again, thanks. Matt
"Tibor Karaszi" wrote:
> Au contraire. With your current setup, you have to first restore the latest database backup, then
> the latest diff backup, then all subsequent log backups.
> With Andrew's suggestion you just restore the latest database backup and then all subsequent log
> backup (same number of log backups as above scenario).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
>
>
|||> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup?
Yes, something like that. Or disk space prohibits you from doing db backups with that frequency...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:B64881EC-6D15-4AFE-ABBF-47BFF7CBCA79@.microsoft.com...[vbcol=seagreen]
> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup? Again, thanks. Matt
> "Tibor Karaszi" wrote:
night. We then do a differential backup every night at 11:00. Additionally we
do transaction log backups every hour from 5:00 in the morning until 9:00 at
night. I recently noticed that my differential backup was about 7 times the
size of my full backup. Does this make sense to anyone else? What could be
causing this? Thanks. Matt
Hi
Are you appending the backup into a single file?
It is best to give every backup a new file, every time it is run.
Regards
Mike
"Matt" wrote:
> I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally we
> do transaction log backups every hour from 5:00 in the morning until 9:00 at
> night. I recently noticed that my differential backup was about 7 times the
> size of my full backup. Does this make sense to anyone else? What could be
> causing this? Thanks. Matt
|||You need to specify the WITH INIT option otherwise it appends each backup to
the prior one. Why not simply do a FULL backup once a night?
Andrew J. Kelly SQL MVP
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>I have a maintenance plan set up so that we do a full backup every Sunday
> night. We then do a differential backup every night at 11:00. Additionally
> we
> do transaction log backups every hour from 5:00 in the morning until 9:00
> at
> night. I recently noticed that my differential backup was about 7 times
> the
> size of my full backup. Does this make sense to anyone else? What could
> be
> causing this? Thanks. Matt
|||Would it not be faster to restore with my current setup? If not, then I
probably will just go to a Full backup every night. Thanks.
"Andrew J. Kelly" wrote:
> You need to specify the WITH INIT option otherwise it appends each backup to
> the prior one. Why not simply do a FULL backup once a night?
> --
> Andrew J. Kelly SQL MVP
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:443B1E93-6FFE-4A06-8D32-4DF540B03125@.microsoft.com...
>
>
|||> Would it not be faster to restore with my current setup?
Au contraire. With your current setup, you have to first restore the latest database backup, then
the latest diff backup, then all subsequent log backups.
With Andrew's suggestion you just restore the latest database backup and then all subsequent log
backup (same number of log backups as above scenario).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...[vbcol=seagreen]
> Would it not be faster to restore with my current setup? If not, then I
> probably will just go to a Full backup every night. Thanks.
> "Andrew J. Kelly" wrote:
|||Thanks to everyone for your help. I assume the only reason to use
differential backups is if you don't have a very big window to do a full
backup? Again, thanks. Matt
"Tibor Karaszi" wrote:
> Au contraire. With your current setup, you have to first restore the latest database backup, then
> the latest diff backup, then all subsequent log backups.
> With Andrew's suggestion you just restore the latest database backup and then all subsequent log
> backup (same number of log backups as above scenario).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:ABCDCE9D-67A5-4D70-AFCA-20B51E3ABF79@.microsoft.com...
>
>
|||> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup?
Yes, something like that. Or disk space prohibits you from doing db backups with that frequency...
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:B64881EC-6D15-4AFE-ABBF-47BFF7CBCA79@.microsoft.com...[vbcol=seagreen]
> Thanks to everyone for your help. I assume the only reason to use
> differential backups is if you don't have a very big window to do a full
> backup? Again, thanks. Matt
> "Tibor Karaszi" wrote:
Backup Sizes in Taskpad and Best Practice
Quick question, does anyone know how the backup size of a database is
determined? I am trying to calculate particular size of a database and its
backup size.
SQL Server 2000 database has many types of size calculations, for example
A. Under Properties -- General Tab
1. Size: 124800.78MB
2. Space Available: 64001.71 MB
B. Under Properties -- Data Files Tab
1. Space allocated: 104013 MB
2. Space allocated: 20789 MB
C. Under Taskpad -- General
1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
How do I know the size of the database backup given the info above? What do
people usually practise to minimize the backup size while not impeding the
performance and availability?
Thanks,
C TO
A is the combined physical file sizes of data and log files on teh drive
B is is individual physical file sizes
C shows how much of the lhysical file size is being used by data
I just checked one of my backups and it appears to be the size of my actual
data for both files, not the size of the physical files, which makes sense.
If you want to minimize the size of you backup files as well as the time it
takes, look into a product called SQL Litespeed from Imceda (yes, I am a
reseller, and for good reason)
HTH,
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"C TO" <CTO@.discussions.microsoft.com> wrote in message
news:B28AE393-46E0-49D4-8B59-52DF29ED813A@.microsoft.com...
> Quick question, does anyone know how the backup size of a database is
> determined? I am trying to calculate particular size of a database and its
> backup size.
> SQL Server 2000 database has many types of size calculations, for example
> A. Under Properties -- General Tab
> 1. Size: 124800.78MB
> 2. Space Available: 64001.71 MB
> B. Under Properties -- Data Files Tab
> 1. Space allocated: 104013 MB
> 2. Space allocated: 20789 MB
> C. Under Taskpad -- General
> 1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
> 2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
> How do I know the size of the database backup given the info above? What
> do
> people usually practise to minimize the backup size while not impeding the
> performance and availability?
> Thanks,
> C TO
determined? I am trying to calculate particular size of a database and its
backup size.
SQL Server 2000 database has many types of size calculations, for example
A. Under Properties -- General Tab
1. Size: 124800.78MB
2. Space Available: 64001.71 MB
B. Under Properties -- Data Files Tab
1. Space allocated: 104013 MB
2. Space allocated: 20789 MB
C. Under Taskpad -- General
1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
How do I know the size of the database backup given the info above? What do
people usually practise to minimize the backup size while not impeding the
performance and availability?
Thanks,
C TO
A is the combined physical file sizes of data and log files on teh drive
B is is individual physical file sizes
C shows how much of the lhysical file size is being used by data
I just checked one of my backups and it appears to be the size of my actual
data for both files, not the size of the physical files, which makes sense.
If you want to minimize the size of you backup files as well as the time it
takes, look into a product called SQL Litespeed from Imceda (yes, I am a
reseller, and for good reason)
HTH,
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"C TO" <CTO@.discussions.microsoft.com> wrote in message
news:B28AE393-46E0-49D4-8B59-52DF29ED813A@.microsoft.com...
> Quick question, does anyone know how the backup size of a database is
> determined? I am trying to calculate particular size of a database and its
> backup size.
> SQL Server 2000 database has many types of size calculations, for example
> A. Under Properties -- General Tab
> 1. Size: 124800.78MB
> 2. Space Available: 64001.71 MB
> B. Under Properties -- Data Files Tab
> 1. Space allocated: 104013 MB
> 2. Space allocated: 20789 MB
> C. Under Taskpad -- General
> 1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
> 2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
> How do I know the size of the database backup given the info above? What
> do
> people usually practise to minimize the backup size while not impeding the
> performance and availability?
> Thanks,
> C TO
Backup Sizes in Taskpad and Best Practice
Quick question, does anyone know how the backup size of a database is
determined? I am trying to calculate particular size of a database and its
backup size.
SQL Server 2000 database has many types of size calculations, for example
A. Under Properties -- General Tab
1. Size: 124800.78MB
2. Space Available: 64001.71 MB
B. Under Properties -- Data Files Tab
1. Space allocated: 104013 MB
2. Space allocated: 20789 MB
C. Under Taskpad -- General
1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
How do I know the size of the database backup given the info above? What do
people usually practise to minimize the backup size while not impeding the
performance and availability?
Thanks,
C TOA is the combined physical file sizes of data and log files on teh drive
B is is individual physical file sizes
C shows how much of the lhysical file size is being used by data
I just checked one of my backups and it appears to be the size of my actual
data for both files, not the size of the physical files, which makes sense.
If you want to minimize the size of you backup files as well as the time it
takes, look into a product called SQL Litespeed from Imceda (yes, I am a
reseller, and for good reason)
HTH,
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"C TO" <CTO@.discussions.microsoft.com> wrote in message
news:B28AE393-46E0-49D4-8B59-52DF29ED813A@.microsoft.com...
> Quick question, does anyone know how the backup size of a database is
> determined? I am trying to calculate particular size of a database and its
> backup size.
> SQL Server 2000 database has many types of size calculations, for example
> A. Under Properties -- General Tab
> 1. Size: 124800.78MB
> 2. Space Available: 64001.71 MB
> B. Under Properties -- Data Files Tab
> 1. Space allocated: 104013 MB
> 2. Space allocated: 20789 MB
> C. Under Taskpad -- General
> 1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
> 2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
> How do I know the size of the database backup given the info above? What
> do
> people usually practise to minimize the backup size while not impeding the
> performance and availability?
> Thanks,
> C TO
determined? I am trying to calculate particular size of a database and its
backup size.
SQL Server 2000 database has many types of size calculations, for example
A. Under Properties -- General Tab
1. Size: 124800.78MB
2. Space Available: 64001.71 MB
B. Under Properties -- Data Files Tab
1. Space allocated: 104013 MB
2. Space allocated: 20789 MB
C. Under Taskpad -- General
1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
How do I know the size of the database backup given the info above? What do
people usually practise to minimize the backup size while not impeding the
performance and availability?
Thanks,
C TOA is the combined physical file sizes of data and log files on teh drive
B is is individual physical file sizes
C shows how much of the lhysical file size is being used by data
I just checked one of my backups and it appears to be the size of my actual
data for both files, not the size of the physical files, which makes sense.
If you want to minimize the size of you backup files as well as the time it
takes, look into a product called SQL Litespeed from Imceda (yes, I am a
reseller, and for good reason)
HTH,
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"C TO" <CTO@.discussions.microsoft.com> wrote in message
news:B28AE393-46E0-49D4-8B59-52DF29ED813A@.microsoft.com...
> Quick question, does anyone know how the backup size of a database is
> determined? I am trying to calculate particular size of a database and its
> backup size.
> SQL Server 2000 database has many types of size calculations, for example
> A. Under Properties -- General Tab
> 1. Size: 124800.78MB
> 2. Space Available: 64001.71 MB
> B. Under Properties -- Data Files Tab
> 1. Space allocated: 104013 MB
> 2. Space allocated: 20789 MB
> C. Under Taskpad -- General
> 1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
> 2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
> How do I know the size of the database backup given the info above? What
> do
> people usually practise to minimize the backup size while not impeding the
> performance and availability?
> Thanks,
> C TO
Backup Sizes in Taskpad and Best Practice
Quick question, does anyone know how the backup size of a database is
determined? I am trying to calculate particular size of a database and its
backup size.
SQL Server 2000 database has many types of size calculations, for example
A. Under Properties -- General Tab
1. Size: 124800.78MB
2. Space Available: 64001.71 MB
B. Under Properties -- Data Files Tab
1. Space allocated: 104013 MB
2. Space allocated: 20789 MB
C. Under Taskpad -- General
1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
How do I know the size of the database backup given the info above? What do
people usually practise to minimize the backup size while not impeding the
performance and availability?
Thanks,
C TOA is the combined physical file sizes of data and log files on teh drive
B is is individual physical file sizes
C shows how much of the lhysical file size is being used by data
I just checked one of my backups and it appears to be the size of my actual
data for both files, not the size of the physical files, which makes sense.
If you want to minimize the size of you backup files as well as the time it
takes, look into a product called SQL Litespeed from Imceda (yes, I am a
reseller, and for good reason)
HTH,
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"C TO" <CTO@.discussions.microsoft.com> wrote in message
news:B28AE393-46E0-49D4-8B59-52DF29ED813A@.microsoft.com...
> Quick question, does anyone know how the backup size of a database is
> determined? I am trying to calculate particular size of a database and its
> backup size.
> SQL Server 2000 database has many types of size calculations, for example
> A. Under Properties -- General Tab
> 1. Size: 124800.78MB
> 2. Space Available: 64001.71 MB
> B. Under Properties -- Data Files Tab
> 1. Space allocated: 104013 MB
> 2. Space allocated: 20789 MB
> C. Under Taskpad -- General
> 1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
> 2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
> How do I know the size of the database backup given the info above? What
> do
> people usually practise to minimize the backup size while not impeding the
> performance and availability?
> Thanks,
> C TO
determined? I am trying to calculate particular size of a database and its
backup size.
SQL Server 2000 database has many types of size calculations, for example
A. Under Properties -- General Tab
1. Size: 124800.78MB
2. Space Available: 64001.71 MB
B. Under Properties -- Data Files Tab
1. Space allocated: 104013 MB
2. Space allocated: 20789 MB
C. Under Taskpad -- General
1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
How do I know the size of the database backup given the info above? What do
people usually practise to minimize the backup size while not impeding the
performance and availability?
Thanks,
C TOA is the combined physical file sizes of data and log files on teh drive
B is is individual physical file sizes
C shows how much of the lhysical file size is being used by data
I just checked one of my backups and it appears to be the size of my actual
data for both files, not the size of the physical files, which makes sense.
If you want to minimize the size of you backup files as well as the time it
takes, look into a product called SQL Litespeed from Imceda (yes, I am a
reseller, and for good reason)
HTH,
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"C TO" <CTO@.discussions.microsoft.com> wrote in message
news:B28AE393-46E0-49D4-8B59-52DF29ED813A@.microsoft.com...
> Quick question, does anyone know how the backup size of a database is
> determined? I am trying to calculate particular size of a database and its
> backup size.
> SQL Server 2000 database has many types of size calculations, for example
> A. Under Properties -- General Tab
> 1. Size: 124800.78MB
> 2. Space Available: 64001.71 MB
> B. Under Properties -- Data Files Tab
> 1. Space allocated: 104013 MB
> 2. Space allocated: 20789 MB
> C. Under Taskpad -- General
> 1. Data: 104012.56MB | 60445.12MB (Used)| 43567.44MB (Free)
> 2. Transaction Log space: 20788.49MB | 69.09MB (Used)| 20719MB (Free)
> How do I know the size of the database backup given the info above? What
> do
> people usually practise to minimize the backup size while not impeding the
> performance and availability?
> Thanks,
> C TO
Backup sizes
We use LiteSpeed backups and was wondering if there is a way in one of those
msdb backup tables that shows me the size of the compressed backups for each
of my dbs?
If so, whats the query?
All i want to know is name of db and its backup size.Take a look at this script:
http://www.sqlcommunity.com/Default.aspx?grm2id=50&tabid=56
Thank you,
Saleem Hakani (World Wide SQL Server Community)
HTTP://WWW.SQLCOMMUNITY.COM
SQLTips, Scripts, Discussions, Radio, Blogs, Articles and a lot more of SQL
Fun.
"Hassan" wrote:
> We use LiteSpeed backups and was wondering if there is a way in one of those
> msdb backup tables that shows me the size of the compressed backups for each
> of my dbs?
> If so, whats the query?
> All i want to know is name of db and its backup size.
>
>|||Saleem this script shows me the actual database size , but I am using
LiteSpeed backup and when i compare the output of your results to the size
on disk, they are different. Your output gives me the size assuming I do a
native backup and not SQL.
How can i get the sizes of the backups that I am using and in this case
LiteSpeed ? are there special LiteSpeed tables ?
"Saleem Hakani" <SaleemHakani@.discussions.microsoft.com> wrote in message
news:3AE9390E-886F-4CAB-8E3B-F06E0BDB0801@.microsoft.com...
> Take a look at this script:
> http://www.sqlcommunity.com/Default.aspx?grm2id=50&tabid=56
> Thank you,
> Saleem Hakani (World Wide SQL Server Community)
> HTTP://WWW.SQLCOMMUNITY.COM
> SQLTips, Scripts, Discussions, Radio, Blogs, Articles and a lot more of
> SQL
> Fun.
>
> "Hassan" wrote:
>> We use LiteSpeed backups and was wondering if there is a way in one of
>> those
>> msdb backup tables that shows me the size of the compressed backups for
>> each
>> of my dbs?
>> If so, whats the query?
>> All i want to know is name of db and its backup size.
>>sql
msdb backup tables that shows me the size of the compressed backups for each
of my dbs?
If so, whats the query?
All i want to know is name of db and its backup size.Take a look at this script:
http://www.sqlcommunity.com/Default.aspx?grm2id=50&tabid=56
Thank you,
Saleem Hakani (World Wide SQL Server Community)
HTTP://WWW.SQLCOMMUNITY.COM
SQLTips, Scripts, Discussions, Radio, Blogs, Articles and a lot more of SQL
Fun.
"Hassan" wrote:
> We use LiteSpeed backups and was wondering if there is a way in one of those
> msdb backup tables that shows me the size of the compressed backups for each
> of my dbs?
> If so, whats the query?
> All i want to know is name of db and its backup size.
>
>|||Saleem this script shows me the actual database size , but I am using
LiteSpeed backup and when i compare the output of your results to the size
on disk, they are different. Your output gives me the size assuming I do a
native backup and not SQL.
How can i get the sizes of the backups that I am using and in this case
LiteSpeed ? are there special LiteSpeed tables ?
"Saleem Hakani" <SaleemHakani@.discussions.microsoft.com> wrote in message
news:3AE9390E-886F-4CAB-8E3B-F06E0BDB0801@.microsoft.com...
> Take a look at this script:
> http://www.sqlcommunity.com/Default.aspx?grm2id=50&tabid=56
> Thank you,
> Saleem Hakani (World Wide SQL Server Community)
> HTTP://WWW.SQLCOMMUNITY.COM
> SQLTips, Scripts, Discussions, Radio, Blogs, Articles and a lot more of
> SQL
> Fun.
>
> "Hassan" wrote:
>> We use LiteSpeed backups and was wondering if there is a way in one of
>> those
>> msdb backup tables that shows me the size of the compressed backups for
>> each
>> of my dbs?
>> If so, whats the query?
>> All i want to know is name of db and its backup size.
>>sql
Subscribe to:
Posts (Atom)