In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
getting message SUSPECT.
So i created new DB with initial size of 5GB to try to restore 50GB the
original DB & it failed.
Finally i was able to restore, by increasing size to substantial level where
my restore was succesfull. i want to know what i did wrong & why finally it
succeed after increasing size. any help will be highly appreciated
Regarding the corruption:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
As for restore:
You cannot restore into a smaller database. SQL Server need to create or already have database files
with same size as you had when you took the backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com. ..
> In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> getting message SUSPECT.
> So i created new DB with initial size of 5GB to try to restore 50GB the
> original DB & it failed.
> Finally i was able to restore, by increasing size to substantial level where
> my restore was succesfull. i want to know what i did wrong & why finally it
> succeed after increasing size. any help will be highly appreciated
|||Hi Tibor,
Will an autogrow option in 5GB DB work in this scenario?
Thanks,
Sree
"Tibor Karaszi" wrote:
> Regarding the corruption:
> http://www.karaszi.com/SQLServer/inf...suspect_db.asp
> As for restore:
> You cannot restore into a smaller database. SQL Server need to create or already have database files
> with same size as you had when you took the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com. ..
>
|||No. But why did you create the database before the restore. The restore operation does a safety
check. If the database which you are to restore into exists, but the file layout doesn't match, you
get an error. This is so you don't do a mistake. But the restore process can create the database for
you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
the restore command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Will an autogrow option in 5GB DB work in this scenario?
> Thanks,
> Sree
>
> "Tibor Karaszi" wrote:
|||Ya thats correct, but still didnt try this option yet thats why.
Thanks, Tibor.
"Tibor Karaszi" wrote:
> No. But why did you create the database before the restore. The restore operation does a safety
> check. If the database which you are to restore into exists, but the file layout doesn't match, you
> get an error. This is so you don't do a mistake. But the restore process can create the database for
> you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
> the restore command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
> news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
>
Showing posts with label 5gb. Show all posts
Showing posts with label 5gb. Show all posts
Monday, March 19, 2012
DB Restore FAIL
In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
getting message SUSPECT.
So i created new DB with initial size of 5GB to try to restore 50GB the
original DB & it failed.
Finally i was able to restore, by increasing size to substantial level where
my restore was succesfull. i want to know what i did wrong & why finally it
succeed after increasing size. any help will be highly appreciatedRegarding the corruption:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
As for restore:
You cannot restore into a smaller database. SQL Server need to create or already have database files
with same size as you had when you took the backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> getting message SUSPECT.
> So i created new DB with initial size of 5GB to try to restore 50GB the
> original DB & it failed.
> Finally i was able to restore, by increasing size to substantial level where
> my restore was succesfull. i want to know what i did wrong & why finally it
> succeed after increasing size. any help will be highly appreciated|||Hi Tibor,
Will an autogrow option in 5GB DB work in this scenario?
Thanks,
Sree
"Tibor Karaszi" wrote:
> Regarding the corruption:
> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> As for restore:
> You cannot restore into a smaller database. SQL Server need to create or already have database files
> with same size as you had when you took the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> > getting message SUSPECT.
> >
> > So i created new DB with initial size of 5GB to try to restore 50GB the
> > original DB & it failed.
> >
> > Finally i was able to restore, by increasing size to substantial level where
> > my restore was succesfull. i want to know what i did wrong & why finally it
> > succeed after increasing size. any help will be highly appreciated
>|||No. But why did you create the database before the restore. The restore operation does a safety
check. If the database which you are to restore into exists, but the file layout doesn't match, you
get an error. This is so you don't do a mistake. But the restore process can create the database for
you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
the restore command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
> Hi Tibor,
> Will an autogrow option in 5GB DB work in this scenario?
> Thanks,
> Sree
>
> "Tibor Karaszi" wrote:
>> Regarding the corruption:
>> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
>> As for restore:
>> You cannot restore into a smaller database. SQL Server need to create or already have database
>> files
>> with same size as you had when you took the backup.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
>> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
>> > getting message SUSPECT.
>> >
>> > So i created new DB with initial size of 5GB to try to restore 50GB the
>> > original DB & it failed.
>> >
>> > Finally i was able to restore, by increasing size to substantial level where
>> > my restore was succesfull. i want to know what i did wrong & why finally it
>> > succeed after increasing size. any help will be highly appreciated
>>|||Ya thats correct, but still didnt try this option yet thats why.
Thanks, Tibor.
"Tibor Karaszi" wrote:
> No. But why did you create the database before the restore. The restore operation does a safety
> check. If the database which you are to restore into exists, but the file layout doesn't match, you
> get an error. This is so you don't do a mistake. But the restore process can create the database for
> you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
> the restore command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
> news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
> > Hi Tibor,
> >
> > Will an autogrow option in 5GB DB work in this scenario?
> >
> > Thanks,
> > Sree
> >
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> Regarding the corruption:
> >> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> >>
> >> As for restore:
> >> You cannot restore into a smaller database. SQL Server need to create or already have database
> >> files
> >> with same size as you had when you took the backup.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> >> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> >> > getting message SUSPECT.
> >> >
> >> > So i created new DB with initial size of 5GB to try to restore 50GB the
> >> > original DB & it failed.
> >> >
> >> > Finally i was able to restore, by increasing size to substantial level where
> >> > my restore was succesfull. i want to know what i did wrong & why finally it
> >> > succeed after increasing size. any help will be highly appreciated
> >>
> >>
>
getting message SUSPECT.
So i created new DB with initial size of 5GB to try to restore 50GB the
original DB & it failed.
Finally i was able to restore, by increasing size to substantial level where
my restore was succesfull. i want to know what i did wrong & why finally it
succeed after increasing size. any help will be highly appreciatedRegarding the corruption:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
As for restore:
You cannot restore into a smaller database. SQL Server need to create or already have database files
with same size as you had when you took the backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> getting message SUSPECT.
> So i created new DB with initial size of 5GB to try to restore 50GB the
> original DB & it failed.
> Finally i was able to restore, by increasing size to substantial level where
> my restore was succesfull. i want to know what i did wrong & why finally it
> succeed after increasing size. any help will be highly appreciated|||Hi Tibor,
Will an autogrow option in 5GB DB work in this scenario?
Thanks,
Sree
"Tibor Karaszi" wrote:
> Regarding the corruption:
> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> As for restore:
> You cannot restore into a smaller database. SQL Server need to create or already have database files
> with same size as you had when you took the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> > getting message SUSPECT.
> >
> > So i created new DB with initial size of 5GB to try to restore 50GB the
> > original DB & it failed.
> >
> > Finally i was able to restore, by increasing size to substantial level where
> > my restore was succesfull. i want to know what i did wrong & why finally it
> > succeed after increasing size. any help will be highly appreciated
>|||No. But why did you create the database before the restore. The restore operation does a safety
check. If the database which you are to restore into exists, but the file layout doesn't match, you
get an error. This is so you don't do a mistake. But the restore process can create the database for
you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
the restore command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
> Hi Tibor,
> Will an autogrow option in 5GB DB work in this scenario?
> Thanks,
> Sree
>
> "Tibor Karaszi" wrote:
>> Regarding the corruption:
>> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
>> As for restore:
>> You cannot restore into a smaller database. SQL Server need to create or already have database
>> files
>> with same size as you had when you took the backup.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
>> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
>> > getting message SUSPECT.
>> >
>> > So i created new DB with initial size of 5GB to try to restore 50GB the
>> > original DB & it failed.
>> >
>> > Finally i was able to restore, by increasing size to substantial level where
>> > my restore was succesfull. i want to know what i did wrong & why finally it
>> > succeed after increasing size. any help will be highly appreciated
>>|||Ya thats correct, but still didnt try this option yet thats why.
Thanks, Tibor.
"Tibor Karaszi" wrote:
> No. But why did you create the database before the restore. The restore operation does a safety
> check. If the database which you are to restore into exists, but the file layout doesn't match, you
> get an error. This is so you don't do a mistake. But the restore process can create the database for
> you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
> the restore command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
> news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
> > Hi Tibor,
> >
> > Will an autogrow option in 5GB DB work in this scenario?
> >
> > Thanks,
> > Sree
> >
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> Regarding the corruption:
> >> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> >>
> >> As for restore:
> >> You cannot restore into a smaller database. SQL Server need to create or already have database
> >> files
> >> with same size as you had when you took the backup.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> >> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> >> > getting message SUSPECT.
> >> >
> >> > So i created new DB with initial size of 5GB to try to restore 50GB the
> >> > original DB & it failed.
> >> >
> >> > Finally i was able to restore, by increasing size to substantial level where
> >> > my restore was succesfull. i want to know what i did wrong & why finally it
> >> > succeed after increasing size. any help will be highly appreciated
> >>
> >>
>
DB Restore FAIL
In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
getting message SUSPECT.
So i created new DB with initial size of 5GB to try to restore 50GB the
original DB & it failed.
Finally i was able to restore, by increasing size to substantial level where
my restore was succesfull. i want to know what i did wrong & why finally it
succeed after increasing size. any help will be highly appreciatedRegarding the corruption:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
As for restore:
You cannot restore into a smaller database. SQL Server need to create or alr
eady have database files
with same size as you had when you took the backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ur
eader.com...
> In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> getting message SUSPECT.
> So i created new DB with initial size of 5GB to try to restore 50GB the
> original DB & it failed.
> Finally i was able to restore, by increasing size to substantial level whe
re
> my restore was succesfull. i want to know what i did wrong & why finally i
t
> succeed after increasing size. any help will be highly appreciated|||Hi Tibor,
Will an autogrow option in 5GB DB work in this scenario?
Thanks,
Sree
"Tibor Karaszi" wrote:
> Regarding the corruption:
> http://www.karaszi.com/SQLServer/in..._suspect_db.asp
> As for restore:
> You cannot restore into a smaller database. SQL Server need to create or a
lready have database files
> with same size as you had when you took the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94
be4@.ureader.com...
>|||No. But why did you create the database before the restore. The restore oper
ation does a safety
check. If the database which you are to restore into exists, but the file la
yout doesn't match, you
get an error. This is so you don't do a mistake. But the restore process can
create the database for
you when you perform the restore operation, it doesn't have to exist. Or, us
e the REPLACE option of
the restore command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Will an autogrow option in 5GB DB work in this scenario?
> Thanks,
> Sree
>
> "Tibor Karaszi" wrote:
>|||Ya thats correct, but still didnt try this option yet thats why.
Thanks, Tibor.
"Tibor Karaszi" wrote:
> No. But why did you create the database before the restore. The restore op
eration does a safety
> check. If the database which you are to restore into exists, but the file
layout doesn't match, you
> get an error. This is so you don't do a mistake. But the restore process c
an create the database for
> you when you perform the restore operation, it doesn't have to exist. Or,
use the REPLACE option of
> the restore command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
> news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
>
getting message SUSPECT.
So i created new DB with initial size of 5GB to try to restore 50GB the
original DB & it failed.
Finally i was able to restore, by increasing size to substantial level where
my restore was succesfull. i want to know what i did wrong & why finally it
succeed after increasing size. any help will be highly appreciatedRegarding the corruption:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
As for restore:
You cannot restore into a smaller database. SQL Server need to create or alr
eady have database files
with same size as you had when you took the backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ur
eader.com...
> In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> getting message SUSPECT.
> So i created new DB with initial size of 5GB to try to restore 50GB the
> original DB & it failed.
> Finally i was able to restore, by increasing size to substantial level whe
re
> my restore was succesfull. i want to know what i did wrong & why finally i
t
> succeed after increasing size. any help will be highly appreciated|||Hi Tibor,
Will an autogrow option in 5GB DB work in this scenario?
Thanks,
Sree
"Tibor Karaszi" wrote:
> Regarding the corruption:
> http://www.karaszi.com/SQLServer/in..._suspect_db.asp
> As for restore:
> You cannot restore into a smaller database. SQL Server need to create or a
lready have database files
> with same size as you had when you took the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94
be4@.ureader.com...
>|||No. But why did you create the database before the restore. The restore oper
ation does a safety
check. If the database which you are to restore into exists, but the file la
yout doesn't match, you
get an error. This is so you don't do a mistake. But the restore process can
create the database for
you when you perform the restore operation, it doesn't have to exist. Or, us
e the REPLACE option of
the restore command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Will an autogrow option in 5GB DB work in this scenario?
> Thanks,
> Sree
>
> "Tibor Karaszi" wrote:
>|||Ya thats correct, but still didnt try this option yet thats why.
Thanks, Tibor.
"Tibor Karaszi" wrote:
> No. But why did you create the database before the restore. The restore op
eration does a safety
> check. If the database which you are to restore into exists, but the file
layout doesn't match, you
> get an error. This is so you don't do a mistake. But the restore process c
an create the database for
> you when you perform the restore operation, it doesn't have to exist. Or,
use the REPLACE option of
> the restore command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
> news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
>
Friday, February 24, 2012
DB Maintenance Plan
I have a SQL 2000 server that has a small but very important database (about 5GB). The current maintenance plan does trans logs every hour and full every day. Currently they are to file on the same drive array. I would like to send them to a share on another server just to be really safe.
Would it be better to
1. Redirect the maintenance plan so that trans logs and backups go directly to the share
or
2. Keep the maintenance plan back ups to the current location and write a script that runs every hour and copies the .bak files to the share.
Also, since the database is so small should I just do full backups every hour instead of transaction?
Hi,
assuming your DB recovery model is full , perform T-Log backup on hourly interval and daily differential backup and weekly full backup....
but ultimately its upto your requirement performing T-Log backup regularly will helps you recover point in time.
Regards
Hemantgiri S. Goswami
|||Thanks for the tip regarding backup types.
What about getting the backups off of the SQL server? Should I redirect them during the backup process or should I let them go to a local drive and them copy them elsewhere?
|||Hi,
Copy them on Network after taking backup on local drive. The reason is suppose their is a network congession or slow network connection while you taking backup dirctly on Network Drive you may get poor response and might be fails to write backup.
Refer below links for more
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=936771&SiteID=1
http://searchsqlserver.techtarget.com/featuredTopic/0,290042,sid87_gci1144141,00.html
http://www.lazydba.com/sql/1__849.html
http://www.windowsitpro.com/Article/ArticleID/14025/14025.html
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=6096
HTH
Hemantgiri S. Goswami
DB Maintenance Plan
I have a SQL 2000 server that has a small but very important database (about 5GB). The current maintenance plan does trans logs every hour and full every day. Currently they are to file on the same drive array. I would like to send them to a share on another server just to be really safe.
Would it be better to
1. Redirect the maintenance plan so that trans logs and backups go directly to the share
or
2. Keep the maintenance plan back ups to the current location and write a script that runs every hour and copies the .bak files to the share.
Also, since the database is so small should I just do full backups every hour instead of transaction?
Hi,
assuming your DB recovery model is full , perform T-Log backup on hourly interval and daily differential backup and weekly full backup....
but ultimately its upto your requirement performing T-Log backup regularly will helps you recover point in time.
Regards
Hemantgiri S. Goswami
|||Thanks for the tip regarding backup types.
What about getting the backups off of the SQL server? Should I redirect them during the backup process or should I let them go to a local drive and them copy them elsewhere?
|||Hi,
Copy them on Network after taking backup on local drive. The reason is suppose their is a network congession or slow network connection while you taking backup dirctly on Network Drive you may get poor response and might be fails to write backup.
Refer below links for more
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=936771&SiteID=1
http://searchsqlserver.techtarget.com/featuredTopic/0,290042,sid87_gci1144141,00.html
http://www.lazydba.com/sql/1__849.html
http://www.windowsitpro.com/Article/ArticleID/14025/14025.html
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=6096
HTH
Hemantgiri S. Goswami
Subscribe to:
Posts (Atom)