Full Recovery

I have a production DB that is in Simple recovery mode. I want to change it
to Full Recovery mode. Are there any settings that i should change before
switching such as from MULTI to SINGLE_USER mode. Will this affect the
current maintenance plans, backup jobs that i have currently running? The
bottomline is that "is it as simple as changing it to Full recovery in
database properties? Thanks...Yes, it is that simple. But you need to make sure you perform regular transa
ction log backups when
in full mode (this is the reason to have it in full).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mmc" <mmc@.discussions.microsoft.com> wrote in message
news:DCA5CC99-1ECB-49E2-90C3-FB7440A4BE34@.microsoft.com...
>I have a production DB that is in Simple recovery mode. I want to change it
> to Full Recovery mode. Are there any settings that i should change before
> switching such as from MULTI to SINGLE_USER mode. Will this affect the
> current maintenance plans, backup jobs that i have currently running? The
> bottomline is that "is it as simple as changing it to Full recovery in
> database properties? Thanks...|||mmc wrote:
> I have a production DB that is in Simple recovery mode. I want to change i
t
> to Full Recovery mode. Are there any settings that i should change before
> switching such as from MULTI to SINGLE_USER mode. Will this affect the
> current maintenance plans, backup jobs that i have currently running? The
> bottomline is that "is it as simple as changing it to Full recovery in
> database properties? Thanks...
You'll need to schedule periodic transaction log backups, otherwise the
transaction log will never get flushed out and will continue to grow as
new transactions are created.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" job
?
"Tracy McKibben" wrote:

> mmc wrote:
> You'll need to schedule periodic transaction log backups, otherwise the
> transaction log will never get flushed out and will continue to grow as
> new transactions are created.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" j
ob?
No. Shrinking a file is not the same as emptying it. You can try to shrink t
he file all you want,
but that will not reduce the number of log records in the file...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"mmc" <mmc@.discussions.microsoft.com> wrote in message
news:029D7C74-7478-4CA4-A4C4-01529B9B71C0@.microsoft.com...[vbcol=seagreen]
> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" j
ob?
> "Tracy McKibben" wrote:
>|||mmc wrote:
> Could the log growth be handled by creating a "Shrinkfile" or "Shrinkdb" j
ob?
>
Nope. Shrinking removes free space from the files, it doesn't remove
committed transactions. Backing up the log file will remove the
committed transactions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||And before you can start making transaction log backups, you'll have to make
a full backup.
You should do that as soon as you make the switch to full mode.
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OlQotFyEHHA.2356@.TK2MSFTNGP03.phx.gbl...
> Yes, it is that simple. But you need to make sure you perform regular
> transaction log backups when in full mode (this is the reason to have it
> in full).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "mmc" <mmc@.discussions.microsoft.com> wrote in message
> news:DCA5CC99-1ECB-49E2-90C3-FB7440A4BE34@.microsoft.com...
>