sql backup files: mydb

Showing posts with label mydb. Show all posts

Sunday, March 11, 2012

Backup Planning SQL2000

Hi i have implemented this backup strategy :
1 - 00:00 AM Backup FULL "myDB"
2 - 06:00 AM Backup T-LOG Overwrite and "NO" to Remove inactive entries
from Transaction Log
3 - 12:00 PM Backup T-LOG Overwrite and "NO" to Remove inactive entries
from Transaction Log
4- 18:00 PM Backup T-LOG Overwrite and "Yes" to Remove inactive entries
from Transaction Log
Shrink T-LOG
My Rocovery model for "MyDB"is "Full"
If my DB crash at 14:00 PM may i restore a FULL Backup of my DB (at 00:00
time) and restore a backup of T-LOg (at 12:00) and recover all information
from 00:00 AM to 12:00 PM ?!'!
In to Job 4 is corrected that i backup my T-LOG with "Remove inactive
entries from Transaction Log" enable and in the same job (after backup) i
shrink t-log ro recover a space ?
Thanks in advance.I would go for the following option
00:00 Full backup
06:00 Log backup - The log is backed up from the last successfully
executed log backup or full backup to the current end of the log. Once the
log is backed up the space may be truncated when no longer required by a
transaction or replication.
12:00 Log backup
If @. 14:00 the system crashes I will restore the full backup followed by
6:00 and 12:00 logs. (This way the transaction log remais small and do not
have to shrink)
Other option could be
00:00 Full backup
06:00 Differential
12:00 Differential
If @. 14:00 the system crashes, I would restore Full backup and 12:00 copies.
I am not sure as to why you would like to specifically want to keep inactive
transactions.
HTH.
Bhanu.
.
<io.com> wrote in message news:#x3hNATtEHA.2516@.TK2MSFTNGP11.phx.gbl...
> Hi i have implemented this backup strategy :
> 1 - 00:00 AM Backup FULL "myDB"
> 2 - 06:00 AM Backup T-LOG Overwrite and "NO" to Remove inactive entries
> from Transaction Log
> 3 - 12:00 PM Backup T-LOG Overwrite and "NO" to Remove inactive entries
> from Transaction Log
> 4- 18:00 PM Backup T-LOG Overwrite and "Yes" to Remove inactive entries
> from Transaction Log
> Shrink T-LOG
>
> My Rocovery model for "MyDB"is "Full"
> If my DB crash at 14:00 PM may i restore a FULL Backup of my DB (at 00:00
> time) and restore a backup of T-LOg (at 12:00) and recover all
information
> from 00:00 AM to 12:00 PM ?!'!
> In to Job 4 is corrected that i backup my T-LOG with "Remove inactive
> entries from Transaction Log" enable and in the same job (after backup) i
> shrink t-log ro recover a space ?
> Thanks in advance.
>|||Thanks for your reply !
Sorry i have a last question :
If i backup only a datafile and the db crash may i restore a db backup and
restore a copy a .ldf file (no backup of logfile but only .ldf file) !'!?
Thanks.
"Bhanu" <SQLDBA1999@.yahoo.com> wrote in message
news:eAdlBGUtEHA.3216@.TK2MSFTNGP15.phx.gbl...
> I would go for the following option
> 00:00 Full backup
> 06:00 Log backup - The log is backed up from the last successfully
> executed log backup or full backup to the current end of the log. Once
the
> log is backed up the space may be truncated when no longer required by a
> transaction or replication.
> 12:00 Log backup
>
> If @. 14:00 the system crashes I will restore the full backup followed by
> 6:00 and 12:00 logs. (This way the transaction log remais small and do
not
> have to shrink)
> Other option could be
> 00:00 Full backup
> 06:00 Differential
> 12:00 Differential
> If @. 14:00 the system crashes, I would restore Full backup and 12:00
copies.
>
> I am not sure as to why you would like to specifically want to keep
inactive
> transactions.
> HTH.
> Bhanu.
>
> .
>
> <io.com> wrote in message news:#x3hNATtEHA.2516@.TK2MSFTNGP11.phx.gbl...
> > Hi i have implemented this backup strategy :
> >
> > 1 - 00:00 AM Backup FULL "myDB"
> > 2 - 06:00 AM Backup T-LOG Overwrite and "NO" to Remove inactive entries
> > from Transaction Log
> > 3 - 12:00 PM Backup T-LOG Overwrite and "NO" to Remove inactive entries
> > from Transaction Log
> > 4- 18:00 PM Backup T-LOG Overwrite and "Yes" to Remove inactive
entries
> > from Transaction Log
> > Shrink T-LOG
> >
> >
> > My Rocovery model for "MyDB"is "Full"
> >
> > If my DB crash at 14:00 PM may i restore a FULL Backup of my DB (at
00:00
> > time) and restore a backup of T-LOg (at 12:00) and recover all
> information
> > from 00:00 AM to 12:00 PM ?!'!
> >
> > In to Job 4 is corrected that i backup my T-LOG with "Remove inactive
> > entries from Transaction Log" enable and in the same job (after backup)
i
> > shrink t-log ro recover a space ?
> >
> > Thanks in advance.
> >
> >
>|||No. Make certain you do frequent enough transaction log backups. If the database crashes, what you
do, if possible, is to do a *backup* of the log after the database crash. Read about the NO_TRUNCATE
option to the BACKUP LOG command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<io.com> wrote in message news:e71Ua$UtEHA.904@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply !
> Sorry i have a last question :
> If i backup only a datafile and the db crash may i restore a db backup and
> restore a copy a .ldf file (no backup of logfile but only .ldf file) !'!?
> Thanks.
> "Bhanu" <SQLDBA1999@.yahoo.com> wrote in message
> news:eAdlBGUtEHA.3216@.TK2MSFTNGP15.phx.gbl...
>> I would go for the following option
>> 00:00 Full backup
>> 06:00 Log backup - The log is backed up from the last successfully
>> executed log backup or full backup to the current end of the log. Once
> the
>> log is backed up the space may be truncated when no longer required by a
>> transaction or replication.
>> 12:00 Log backup
>>
>> If @. 14:00 the system crashes I will restore the full backup followed by
>> 6:00 and 12:00 logs. (This way the transaction log remais small and do
> not
>> have to shrink)
>> Other option could be
>> 00:00 Full backup
>> 06:00 Differential
>> 12:00 Differential
>> If @. 14:00 the system crashes, I would restore Full backup and 12:00
> copies.
>>
>> I am not sure as to why you would like to specifically want to keep
> inactive
>> transactions.
>> HTH.
>> Bhanu.
>>
>> .
>>
>> <io.com> wrote in message news:#x3hNATtEHA.2516@.TK2MSFTNGP11.phx.gbl...
>> > Hi i have implemented this backup strategy :
>> >
>> > 1 - 00:00 AM Backup FULL "myDB"
>> > 2 - 06:00 AM Backup T-LOG Overwrite and "NO" to Remove inactive entries
>> > from Transaction Log
>> > 3 - 12:00 PM Backup T-LOG Overwrite and "NO" to Remove inactive entries
>> > from Transaction Log
>> > 4- 18:00 PM Backup T-LOG Overwrite and "Yes" to Remove inactive
> entries
>> > from Transaction Log
>> > Shrink T-LOG
>> >
>> >
>> > My Rocovery model for "MyDB"is "Full"
>> >
>> > If my DB crash at 14:00 PM may i restore a FULL Backup of my DB (at
> 00:00
>> > time) and restore a backup of T-LOg (at 12:00) and recover all
>> information
>> > from 00:00 AM to 12:00 PM ?!'!
>> >
>> > In to Job 4 is corrected that i backup my T-LOG with "Remove inactive
>> > entries from Transaction Log" enable and in the same job (after backup)
> i
>> > shrink t-log ro recover a space ?
>> >
>> > Thanks in advance.
>> >
>> >
>>
>|||<io.com> wrote in message news:%23x3hNATtEHA.2516@.TK2MSFTNGP11.phx.gbl...
> Hi i have implemented this backup strategy :
> 1 - 00:00 AM Backup FULL "myDB"
> 2 - 06:00 AM Backup T-LOG Overwrite and "NO" to Remove inactive entries
> from Transaction Log
> 3 - 12:00 PM Backup T-LOG Overwrite and "NO" to Remove inactive entries
> from Transaction Log
> 4- 18:00 PM Backup T-LOG Overwrite and "Yes" to Remove inactive entries
> from Transaction Log
> Shrink T-LOG
Besides other comments, I'd skip the "Shrink T-LOG" step. Only thing it
really can do is lead to fragmentation of the disk.
>
> My Rocovery model for "MyDB"is "Full"
> If my DB crash at 14:00 PM may i restore a FULL Backup of my DB (at 00:00
> time) and restore a backup of T-LOg (at 12:00) and recover all
information
> from 00:00 AM to 12:00 PM ?!'!
> In to Job 4 is corrected that i backup my T-LOG with "Remove inactive
> entries from Transaction Log" enable and in the same job (after backup) i
> shrink t-log ro recover a space ?
> Thanks in advance.
>

Backup Planning SQL2000

Thursday, March 8, 2012

Backup Plan advice / suggestion

Hello guys,
I would like to know if someone can advice me on that.
I have A MyDB more system DB (master, msdb, model, tempdb)
I would like to set up a Backup plan.
I would like to:
* Backup daily MyDB and system DB
* Backup LOG MyDB every one hours
* Backup LOG System DB (every 4 hours).
Any suggestion how to plan the better schedule time? 22h? 23h for
backup?
InaSee responses in-line...
ina wrote:
> Hello guys,
> I would like to know if someone can advice me on that.
> I have A MyDB more system DB (master, msdb, model, tempdb)
> I would like to set up a Backup plan.
> I would like to:
> * Backup daily MyDB and system DB
No need to backup TEMPDB or MODEL, unless you have modified MODEL.
> * Backup LOG MyDB every one hours
This depends on your needs and tolerance for risk. You could
*potentially* lose an hour's worth of data, is that an acceptable risk
for you?
> * Backup LOG System DB (every 4 hours).
The only system DB that you can perform log backups on is MSDB, and this
is probably unnecessary.
> Any suggestion how to plan the better schedule time? 22h? 23h for
> backup?
> Ina
>
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
> No need to backup TEMPDB or MODEL, unless you have modified MODEL.
What is model crashes? If you have a backup, you just restore that backup. If not, you have to
rebuild the system databases (or do something unsupported like grabbing the files from another
system and worry about collations, if it works etc). This is why I always include database backup of
model in my backups schedules.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45264804.8030302@.realsqlguy.com...
> See responses in-line...
>
> ina wrote:
>> Hello guys,
>> I would like to know if someone can advice me on that.
>> I have A MyDB more system DB (master, msdb, model, tempdb)
>> I would like to set up a Backup plan.
>> I would like to:
>> * Backup daily MyDB and system DB
> No need to backup TEMPDB or MODEL, unless you have modified MODEL.
>> * Backup LOG MyDB every one hours
> This depends on your needs and tolerance for risk. You could *potentially* lose an hour's worth
> of data, is that an acceptable risk for you?
>> * Backup LOG System DB (every 4 hours).
> The only system DB that you can perform log backups on is MSDB, and this is probably unnecessary.
>> Any suggestion how to plan the better schedule time? 22h? 23h for
>> backup?
>> Ina
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Thank you.
what I am doing now it is the full backup for MyDB at 11 PM and log
files this MyDB every hours between 2 AM until 10 PM
Is it fine?
Ina
Tibor Karaszi wrote:
> Hi Tracy,
> > No need to backup TEMPDB or MODEL, unless you have modified MODEL.
> What is model crashes? If you have a backup, you just restore that backup. If not, you have to
> rebuild the system databases (or do something unsupported like grabbing the files from another
> system and worry about collations, if it works etc). This is why I always include database backup of
> model in my backups schedules.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45264804.8030302@.realsqlguy.com...
> > See responses in-line...
> >
> >
> > ina wrote:
> >> Hello guys,
> >>
> >> I would like to know if someone can advice me on that.
> >>
> >> I have A MyDB more system DB (master, msdb, model, tempdb)
> >> I would like to set up a Backup plan.
> >> I would like to:
> >> * Backup daily MyDB and system DB
> >
> > No need to backup TEMPDB or MODEL, unless you have modified MODEL.
> >
> >> * Backup LOG MyDB every one hours
> >
> > This depends on your needs and tolerance for risk. You could *potentially* lose an hour's worth
> > of data, is that an acceptable risk for you?
> >
> >> * Backup LOG System DB (every 4 hours).
> >
> > The only system DB that you can perform log backups on is MSDB, and this is probably unnecessary.
> >
> >>
> >> Any suggestion how to plan the better schedule time? 22h? 23h for
> >> backup?
> >>
> >> Ina
> >>
> >
> >
> > --
> > Tracy McKibben
> > MCDBA
> > http://www.realsqlguy.com|||> what I am doing now it is the full backup for MyDB at 11 PM and log
> files this MyDB every hours between 2 AM until 10 PM
I assume you mean "transaction log backup every hour between 2AB and 10PM".
> Is it fine?
We cannot answer that question. You have to determine that max amount of data loss you accept in
case of some catastrophe and based on that determine what types of backup and frequency. Also, you
didn't mention what backup you do if the system databases.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1160222216.686213.118770@.e3g2000cwe.googlegroups.com...
> Thank you.
> what I am doing now it is the full backup for MyDB at 11 PM and log
> files this MyDB every hours between 2 AM until 10 PM
> Is it fine?
> Ina
> Tibor Karaszi wrote:
>> Hi Tracy,
>> > No need to backup TEMPDB or MODEL, unless you have modified MODEL.
>> What is model crashes? If you have a backup, you just restore that backup. If not, you have to
>> rebuild the system databases (or do something unsupported like grabbing the files from another
>> system and worry about collations, if it works etc). This is why I always include database backup
>> of
>> model in my backups schedules.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45264804.8030302@.realsqlguy.com...
>> > See responses in-line...
>> >
>> >
>> > ina wrote:
>> >> Hello guys,
>> >>
>> >> I would like to know if someone can advice me on that.
>> >>
>> >> I have A MyDB more system DB (master, msdb, model, tempdb)
>> >> I would like to set up a Backup plan.
>> >> I would like to:
>> >> * Backup daily MyDB and system DB
>> >
>> > No need to backup TEMPDB or MODEL, unless you have modified MODEL.
>> >
>> >> * Backup LOG MyDB every one hours
>> >
>> > This depends on your needs and tolerance for risk. You could *potentially* lose an hour's
>> > worth
>> > of data, is that an acceptable risk for you?
>> >
>> >> * Backup LOG System DB (every 4 hours).
>> >
>> > The only system DB that you can perform log backups on is MSDB, and this is probably
>> > unnecessary.
>> >
>> >>
>> >> Any suggestion how to plan the better schedule time? 22h? 23h for
>> >> backup?
>> >>
>> >> Ina
>> >>
>> >
>> >
>> > --
>> > Tracy McKibben
>> > MCDBA
>> > http://www.realsqlguy.com
>|||Thanks Tibor,
My DB is organize like this everyday I backup Master, Model and Msdb
and every hours a back up the log of Mdsb
For my MyDB is the same backup everyday and backup log every hours.
One question when I change the schedule of the backup (i.e MyDB log
backup) do you thing is better to change backup file or device or it
is enough to change the schedule?
Ina
Tibor Karaszi wrote:
> > what I am doing now it is the full backup for MyDB at 11 PM and log
> > files this MyDB every hours between 2 AM until 10 PM
> I assume you mean "transaction log backup every hour between 2AB and 10PM".
>
> > Is it fine?
> We cannot answer that question. You have to determine that max amount of data loss you accept in
> case of some catastrophe and based on that determine what types of backup and frequency. Also, you
> didn't mention what backup you do if the system databases.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1160222216.686213.118770@.e3g2000cwe.googlegroups.com...
> > Thank you.
> >
> > what I am doing now it is the full backup for MyDB at 11 PM and log
> > files this MyDB every hours between 2 AM until 10 PM
> >
> > Is it fine?
> >
> > Ina
> > Tibor Karaszi wrote:
> >> Hi Tracy,
> >>
> >> > No need to backup TEMPDB or MODEL, unless you have modified MODEL.
> >>
> >> What is model crashes? If you have a backup, you just restore that backup. If not, you have to
> >> rebuild the system databases (or do something unsupported like grabbing the files from another
> >> system and worry about collations, if it works etc). This is why I always include database backup
> >> of
> >> model in my backups schedules.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45264804.8030302@.realsqlguy.com...
> >> > See responses in-line...
> >> >
> >> >
> >> > ina wrote:
> >> >> Hello guys,
> >> >>
> >> >> I would like to know if someone can advice me on that.
> >> >>
> >> >> I have A MyDB more system DB (master, msdb, model, tempdb)
> >> >> I would like to set up a Backup plan.
> >> >> I would like to:
> >> >> * Backup daily MyDB and system DB
> >> >
> >> > No need to backup TEMPDB or MODEL, unless you have modified MODEL.
> >> >
> >> >> * Backup LOG MyDB every one hours
> >> >
> >> > This depends on your needs and tolerance for risk. You could *potentially* lose an hour's
> >> > worth
> >> > of data, is that an acceptable risk for you?
> >> >
> >> >> * Backup LOG System DB (every 4 hours).
> >> >
> >> > The only system DB that you can perform log backups on is MSDB, and this is probably
> >> > unnecessary.
> >> >
> >> >>
> >> >> Any suggestion how to plan the better schedule time? 22h? 23h for
> >> >> backup?
> >> >>
> >> >> Ina
> >> >>
> >> >
> >> >
> >> > --
> >> > Tracy McKibben
> >> > MCDBA
> >> > http://www.realsqlguy.com
> >

Sunday, February 19, 2012

BACKUP LOG WITH TRUNCATE_ONLY after DBCC SHRINKDATABASE

Is there any benefit to performing a BACKUP LOG MyDB WITH TRUNCATE_ONLY
after a DBCC SHRINKDATABASE (N'MyDB', 10, NOTRUNCATE) on a database where
the recovery model is simple?
DaveHi Dave
In SIMPLE mode, SQL Server performs the same operation automatically at
regular frequent intervals, so there would be practically no benefit to
doing it yourself.
But, a related question is, WHY are you shrinking the database? Most people
think they need to shrink in order to reclaim space, but with the NOTRUNCATE
option you're not even going to get that.
Please read this article:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"DaveF" <dave@.aol.com> wrote in message news:5qIrj.2329$ip3.859@.trnddc07...
> Is there any benefit to performing a BACKUP LOG MyDB WITH TRUNCATE_ONLY
> after a DBCC SHRINKDATABASE (N'MyDB', 10, NOTRUNCATE) on a database where
> the recovery model is simple?
> Dave
>|||Kalen,
We have a data warehouse load routine written by our software vendor that
actually performs 7 database shrinks over the course of the nightly run.
Believe it or not.
Are you saying these aren't necessary?
FYI. Our dev and test databases are in simple mode but our production
database is in full mode.
Dave
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:%23JPpvkCbIHA.5400@.TK2MSFTNGP03.phx.gbl...
> Hi Dave
> In SIMPLE mode, SQL Server performs the same operation automatically at
> regular frequent intervals, so there would be practically no benefit to
> doing it yourself.
> But, a related question is, WHY are you shrinking the database? Most
> people think they need to shrink in order to reclaim space, but with the
> NOTRUNCATE option you're not even going to get that.
> Please read this article:
> http://www.karaszi.com/sqlserver/info_dont_shrink.asp
>
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "DaveF" <dave@.aol.com> wrote in message
> news:5qIrj.2329$ip3.859@.trnddc07...
>> Is there any benefit to performing a BACKUP LOG MyDB WITH TRUNCATE_ONLY
>> after a DBCC SHRINKDATABASE (N'MyDB', 10, NOTRUNCATE) on a database
>> where the recovery model is simple?
>> Dave
>|||Did you read the article I pointed you to?
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"DaveF" <dave@.aol.com> wrote in message news:tYNrj.1262$r03.293@.trnddc08...
> Kalen,
> We have a data warehouse load routine written by our software vendor that
> actually performs 7 database shrinks over the course of the nightly run.
> Believe it or not.
> Are you saying these aren't necessary?
> FYI. Our dev and test databases are in simple mode but our production
> database is in full mode.
> Dave
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:%23JPpvkCbIHA.5400@.TK2MSFTNGP03.phx.gbl...
>> Hi Dave
>> In SIMPLE mode, SQL Server performs the same operation automatically at
>> regular frequent intervals, so there would be practically no benefit to
>> doing it yourself.
>> But, a related question is, WHY are you shrinking the database? Most
>> people think they need to shrink in order to reclaim space, but with the
>> NOTRUNCATE option you're not even going to get that.
>> Please read this article:
>> http://www.karaszi.com/sqlserver/info_dont_shrink.asp
>>
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "DaveF" <dave@.aol.com> wrote in message
>> news:5qIrj.2329$ip3.859@.trnddc07...
>> Is there any benefit to performing a BACKUP LOG MyDB WITH TRUNCATE_ONLY
>> after a DBCC SHRINKDATABASE (N'MyDB', 10, NOTRUNCATE) on a database
>> where the recovery model is simple?
>> Dave
>>
>|||Time to get a new vendor.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"DaveF" <dave@.aol.com> wrote in message news:tYNrj.1262$r03.293@.trnddc08...
> Kalen,
> We have a data warehouse load routine written by our software vendor that
> actually performs 7 database shrinks over the course of the nightly run.
> Believe it or not.
> Are you saying these aren't necessary?
> FYI. Our dev and test databases are in simple mode but our production
> database is in full mode.
> Dave
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:%23JPpvkCbIHA.5400@.TK2MSFTNGP03.phx.gbl...
>> Hi Dave
>> In SIMPLE mode, SQL Server performs the same operation automatically at
>> regular frequent intervals, so there would be practically no benefit to
>> doing it yourself.
>> But, a related question is, WHY are you shrinking the database? Most
>> people think they need to shrink in order to reclaim space, but with the
>> NOTRUNCATE option you're not even going to get that.
>> Please read this article:
>> http://www.karaszi.com/sqlserver/info_dont_shrink.asp
>>
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "DaveF" <dave@.aol.com> wrote in message
>> news:5qIrj.2329$ip3.859@.trnddc07...
>> Is there any benefit to performing a BACKUP LOG MyDB WITH TRUNCATE_ONLY
>> after a DBCC SHRINKDATABASE (N'MyDB', 10, NOTRUNCATE) on a database
>> where the recovery model is simple?
>> Dave
>>
>

Sunday, March 11, 2012

Backup Planning SQL2000

Backup Planning SQL2000

Backup Planning SQL2000

Thursday, March 8, 2012

Backup Plan advice / suggestion

Backup Plan advice / suggestion

Backup Plan advice / suggestion

Sunday, February 19, 2012

BACKUP LOG WITH TRUNCATE_ONLY after DBCC SHRINKDATABASE

BACKUP LOG WITH TRUNCATE_ONLY after DBCC SHRINKDATABASE

sql backup files

Blog Archive

About Me