60 days of backups

I have had a request to run backups of a database to disk, and retain the
backups until they are 60 days old. I've got the job set up, but it either
appends or overwrites the previous job. Does anyone know of a way to do
this?
TIA,
KSee
http://www.nigelrivett.net/BackupAllDatabases.html
You could use the sqlmaint exe but I think backups are too
important.
>--Original Message--
>I have had a request to run backups of a database to
disk, and retain the
>backups until they are 60 days old. I've got the job set
up, but it either
>appends or overwrites the previous job. Does anyone know
of a way to do
>this?
>TIA,
>K
>
>.
>|||Use the maintenance function in SLQ and enable the SQL server agent service
--
J
www.urbanvoyeur.com
"msnews.microsoft.com" <kb@.blah.com> wrote in message
news:uet5nU7iDHA.1696@.TK2MSFTNGP12.phx.gbl...
> I have had a request to run backups of a database to disk, and retain the
> backups until they are 60 days old. I've got the job set up, but it
either
> appends or overwrites the previous job. Does anyone know of a way to do
> this?
> TIA,
> K
>|||Thanks for the help...I setup a maintenance plan and have my fingers crossed
that this will work!
K
"UrbanVoyeur" <nospam@.nospam.com> wrote in message
news:ey9Bi4AjDHA.1676@.TK2MSFTNGP09.phx.gbl...
> Use the maintenance function in SLQ and enable the SQL server agent
service
> --
> J
> www.urbanvoyeur.com
>
> "msnews.microsoft.com" <kb@.blah.com> wrote in message
> news:uet5nU7iDHA.1696@.TK2MSFTNGP12.phx.gbl...
> > I have had a request to run backups of a database to disk, and retain
the
> > backups until they are 60 days old. I've got the job set up, but it
> either
> > appends or overwrites the previous job. Does anyone know of a way to do
> > this?
> >
> > TIA,
> > K
> >
> >
>

6.5 to 2000 upgrade

We will be performing a 2 machine upgrade from 6.5 to
2000. When I install 2000 on our new server, I want
retain the registed name that I gave the server on the
6.5 box (upon taking the 6.5 box offline and making the
2000 box the "live" box). Can I call both servers the
same name (e.g. testserver)? Do I install SQL 2000 as a
named instance or a default instance? When I perform the
upgrade wizard, will I have the opportunity at that time
to ultimately retain the name? Thanks!No. Only one server can be named the same in a domain at
any given time, so they must be unique.
If it is not a clustered instance and you are installing
locally to a normal server, by default, SQL Server will
take on the name of its underlying server if it is a
default instance. So in essence, if you're using a
default instance, you'd have to name your server the
same. Now, if you completely decomission the old server
and shut it down and then change the name of the newer
server, you should be fine.
The bigger question is will your applications handle a
named instance? That is what you need to determine. You
can only have one default instance per server or cluster.
>--Original Message--
>We will be performing a 2 machine upgrade from 6.5 to
>2000. When I install 2000 on our new server, I want
>retain the registed name that I gave the server on the
>6.5 box (upon taking the 6.5 box offline and making the
>2000 box the "live" box). Can I call both servers the
>same name (e.g. testserver)? Do I install SQL 2000 as a
>named instance or a default instance? When I perform the
>upgrade wizard, will I have the opportunity at that time
>to ultimately retain the name? Thanks!
>.
>