|
|
You're in the
sql server dts
group:SQL Backup
sql server dts:
What do you mean by a fairly regular basis? Once a day, once a week, once
an hour etc? How large are the db's? If it is only once a day or the db's are relatively small I would simply do as you stated and restore the full backup. You can easily scipt a vb or tsql job to do this task. If it's is more frequent you may want to look at Log shipping. You can find more details in BOL. -- Andrew J. Kelly SQL MVP [quoted text, click to view] "Steven Clark" <sjc@Junk.uksupport.net> wrote in message news:413dda55$0$29927$cc9e4d1f@news.dial.pipex.com... > Hi there > > Hope someone can help me with this. I have a number of databases located on > one server which I need to replicate to a backup server on a fairly regular > basis. > > My first thought on doing that was to use SQL replication however I have hit > upon some problems with that. The main one being that a number of the > tables are over the maximum field limit for SQL replication. > > I am therefore looking for suggestions on how best to do this whilst > minimising any extra load put on the server. My thoughts have included > scheduling a regular backup on the source server and then writing a small > app which will copy the backup file from source to destination and then kick > off a restore command but there must be a better way. > > Hope someone can help. > > Steven > >
Hi there
Hope someone can help me with this. I have a number of databases located on one server which I need to replicate to a backup server on a fairly regular basis. My first thought on doing that was to use SQL replication however I have hit upon some problems with that. The main one being that a number of the tables are over the maximum field limit for SQL replication. I am therefore looking for suggestions on how best to do this whilst minimising any extra load put on the server. My thoughts have included scheduling a regular backup on the source server and then writing a small app which will copy the backup file from source to destination and then kick off a restore command but there must be a better way. Hope someone can help. Steven
Fairly regular is about every 30mins to an hour... we need this machine to
be reasonably up to date. The databases are quite large... one is almost 1.6 gig and is growing about 100 meg a week. The other is nearly 400 meg but I can see the size of this growing quickly shortly. I'm just going off to have a look at log shipping. Steven [quoted text, click to view] "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:emm6XCQlEHA.896@TK2MSFTNGP12.phx.gbl... > What do you mean by a fairly regular basis? Once a day, once a week, once > an hour etc? How large are the db's? If it is only once a day or the db's > are relatively small I would simply do as you stated and restore the full > backup. You can easily scipt a vb or tsql job to do this task. If it's is > more frequent you may want to look at Log shipping. You can find more > details in BOL. > > -- > Andrew J. Kelly SQL MVP > > > "Steven Clark" <sjc@Junk.uksupport.net> wrote in message > news:413dda55$0$29927$cc9e4d1f@news.dial.pipex.com... > > Hi there > > > > Hope someone can help me with this. I have a number of databases located > on > > one server which I need to replicate to a backup server on a fairly > regular > > basis. > > > > My first thought on doing that was to use SQL replication however I have > hit > > upon some problems with that. The main one being that a number of the > > tables are over the maximum field limit for SQL replication. > > > > I am therefore looking for suggestions on how best to do this whilst > > minimising any extra load put on the server. My thoughts have included > > scheduling a regular backup on the source server and then writing a small > > app which will copy the backup file from source to destination and then > kick > > off a restore command but there must be a better way. > > > > Hope someone can help. > > > > Steven > > > > > >
You can still write your own log shipping routine and use it
with any edition - Enterprise Edition just has a wizard to set it up for you. You can search the sql server newsgroups using google to find some examples. You can also find more information at: http://www.sql-server-performance.com/sql_server_log_shipping.asp And the SQL Server 2000 Resource Kit has information and scripts for setting up log shipping with it's version called Simple Log Shipper. -Sue On Wed, 8 Sep 2004 00:35:03 +0100, "Steven Clark" [quoted text, click to view] <sjc@Junk.uksupport.net> wrote:
>Sorry to be a pain guys. > >Have just looked at log shipping and that looks ideal but I have a problem >in that we are only running SQL 2000 Standard edition and not enterprise. > >Can any one advise of any way round this or does anyone have any more ideas >as to how this can be achieved. > >Thanks > >Steven > >"Steven Clark" <sjc@Junk.uksupport.net> wrote in message >news:413df5fb$0$29945$cc9e4d1f@news.dial.pipex.com... >> Fairly regular is about every 30mins to an hour... we need this machine to >> be reasonably up to date. >> >> The databases are quite large... one is almost 1.6 gig and is growing >about >> 100 meg a week. The other is nearly 400 meg but I can see the size of >this >> growing quickly shortly. >> >> I'm just going off to have a look at log shipping. >> >> Steven >> >> "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message >> news:emm6XCQlEHA.896@TK2MSFTNGP12.phx.gbl... >> > What do you mean by a fairly regular basis? Once a day, once a week, >once >> > an hour etc? How large are the db's? If it is only once a day or the >> db's >> > are relatively small I would simply do as you stated and restore the >full >> > backup. You can easily scipt a vb or tsql job to do this task. If it's >> is >> > more frequent you may want to look at Log shipping. You can find more >> > details in BOL. >> > >> > -- >> > Andrew J. Kelly SQL MVP >> > >> > >> > "Steven Clark" <sjc@Junk.uksupport.net> wrote in message >> > news:413dda55$0$29927$cc9e4d1f@news.dial.pipex.com... >> > > Hi there >> > > >> > > Hope someone can help me with this. I have a number of databases >> located >> > on >> > > one server which I need to replicate to a backup server on a fairly >> > regular >> > > basis. >> > > >> > > My first thought on doing that was to use SQL replication however I >have >> > hit >> > > upon some problems with that. The main one being that a number of the >> > > tables are over the maximum field limit for SQL replication. >> > > >> > > I am therefore looking for suggestions on how best to do this whilst >> > > minimising any extra load put on the server. My thoughts have >included >> > > scheduling a regular backup on the source server and then writing a >> small >> > > app which will copy the backup file from source to destination and >then >> > kick >> > > off a restore command but there must be a better way. >> > > >> > > Hope someone can help. >> > > >> > > Steven >> > > >> > > >> > >> > >> >> >
Sorry to be a pain guys.
Have just looked at log shipping and that looks ideal but I have a problem in that we are only running SQL 2000 Standard edition and not enterprise. Can any one advise of any way round this or does anyone have any more ideas as to how this can be achieved. Thanks Steven [quoted text, click to view] "Steven Clark" <sjc@Junk.uksupport.net> wrote in message news:413df5fb$0$29945$cc9e4d1f@news.dial.pipex.com... > Fairly regular is about every 30mins to an hour... we need this machine to > be reasonably up to date. > > The databases are quite large... one is almost 1.6 gig and is growing about > 100 meg a week. The other is nearly 400 meg but I can see the size of this > growing quickly shortly. > > I'm just going off to have a look at log shipping. > > Steven > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message > news:emm6XCQlEHA.896@TK2MSFTNGP12.phx.gbl... > > What do you mean by a fairly regular basis? Once a day, once a week, once > > an hour etc? How large are the db's? If it is only once a day or the > db's > > are relatively small I would simply do as you stated and restore the full > > backup. You can easily scipt a vb or tsql job to do this task. If it's > is > > more frequent you may want to look at Log shipping. You can find more > > details in BOL. > > > > -- > > Andrew J. Kelly SQL MVP > > > > > > "Steven Clark" <sjc@Junk.uksupport.net> wrote in message > > news:413dda55$0$29927$cc9e4d1f@news.dial.pipex.com... > > > Hi there > > > > > > Hope someone can help me with this. I have a number of databases > located > > on > > > one server which I need to replicate to a backup server on a fairly > > regular > > > basis. > > > > > > My first thought on doing that was to use SQL replication however I have > > hit > > > upon some problems with that. The main one being that a number of the > > > tables are over the maximum field limit for SQL replication. > > > > > > I am therefore looking for suggestions on how best to do this whilst > > > minimising any extra load put on the server. My thoughts have included > > > scheduling a regular backup on the source server and then writing a > small > > > app which will copy the backup file from source to destination and then > > kick > > > off a restore command but there must be a better way. > > > > > > Hope someone can help. > > > > > > Steven > > > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |