Backup policy for a newbies?

Hi,
I always used SQL server as a developper. I never think about backup Restore
policy. Now a collegue is asking me the best solution. I had this issue when
I was a mainframe programmer, but now ...
I suggest him to do as followed ;monthly or weekly.
Full - Logs - Differential - logs - Differentials - ...
He just agree with my suggestion but let me knows that the logs backup are
growing and growing.
I am quite sure that the solution is to "inform" sql server 2005 that I have
kept a full or diffrential backup and he can scrash his log file and begin a
new one.
Am I wrong and if not, how say to msssql server 2005 that he can begein a
new log file and free the unnecessary space?
Thanks for your help.
Patrick
SQL Server do not work as many of the other products...

> I am quite sure that the solution is to "inform" sql server 2005 that I have
> kept a full or diffrential backup and he can scrash his log file and begin a
> new one.
What log file do you refer to? The file where you backup the log (like .bak) or the "active"
database log file (.ldf).
For the ldf file: No need to inform anything. SQL Server understands that you did a log backup and
will basically empty the ldf file. More information available at
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
For the backup file. SQL Server does not assumes anything. You control whether you want to overwrite
or append using the INIT or NOINIT parameter.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Patrick Sandron" <PatrickSandron@.discussions.microsoft.com> wrote in message
news:79555DF4-0A4E-496F-8736-4350AD2A93BB@.microsoft.com...
> Hi,
> I always used SQL server as a developper. I never think about backup Restore
> policy. Now a collegue is asking me the best solution. I had this issue when
> I was a mainframe programmer, but now ...
> I suggest him to do as followed ;monthly or weekly.
> Full - Logs - Differential - logs - Differentials - ...
> He just agree with my suggestion but let me knows that the logs backup are
> growing and growing.
> I am quite sure that the solution is to "inform" sql server 2005 that I have
> kept a full or diffrential backup and he can scrash his log file and begin a
> new one.
> Am I wrong and if not, how say to msssql server 2005 that he can begein a
> new log file and free the unnecessary space?
> Thanks for your help.
> Patrick
|||Hi
[url]http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1 [/url]
--administaiting best practices
"Patrick Sandron" <PatrickSandron@.discussions.microsoft.com> wrote in
message news:79555DF4-0A4E-496F-8736-4350AD2A93BB@.microsoft.com...
> Hi,
> I always used SQL server as a developper. I never think about backup
> Restore
> policy. Now a collegue is asking me the best solution. I had this issue
> when
> I was a mainframe programmer, but now ...
> I suggest him to do as followed ;monthly or weekly.
> Full - Logs - Differential - logs - Differentials - ...
> He just agree with my suggestion but let me knows that the logs backup are
> growing and growing.
> I am quite sure that the solution is to "inform" sql server 2005 that I
> have
> kept a full or diffrential backup and he can scrash his log file and begin
> a
> new one.
> Am I wrong and if not, how say to msssql server 2005 that he can begein a
> new log file and free the unnecessary space?
> Thanks for your help.
> Patrick