Friday, February 17, 2012
Corruption Problem- need some advice
we have been using SQL7 for a number of years on a Win2K box without so much
as one hiccup. Recently went out bought a new HP Server and SQL2000.
Installed it all, moved all the databases - and everything seemed to be
working fine.
A couple of weeks ago we had a problem with our biggest database (about 1gb
in size). Users were getting some errors from the app that uses it. I did a
DBCC CHECKDB on that database and it was coming up with almost 1000
inconsistencies etc etc. Tried Repair, to no avail and in the end just had
to Restore form backup - lost about a half a days work - not critical for
us.
Spoke to a few DBA's who said that it sounded Hardware related. Spoke to our
local IT support who we got the HP's from and they did a quick look and
everything came up OK.
A couple of days ago the same problem occurred. At a loss to explain what is
happening, so I'm hoping a few of you may be able to help.
One thing I did notice was that Write Cache was set on the server to 50%
Read 50% Write. I have only now changed it to 100% and No Write caching.
Could the above have caused it (50% Read 50% Write), or is it more than
likely I could have further corruption ? We haven't , I believe, had any
power outages or system crashes leading up to these corruptions.
Any help you could give me would be greatly appreciated.
cheers,
Adam
Adam,
While it's quite possible that you are hitting some SQL bug which corrupts
your database, it is far more likely that you may have some hardware or
driver related problem on that server. I would advise you to install the
latest SQL hotfix and update all your firmware and drivers. If you have
enabled /PAE in BOOT.INI then apply the PAE fix Q838765. Also review your
event logs in detail for ANY hardware-related errors and warnings. Use
SQLIOSTRESS to try to flush out I/O problems.
Going to the latest SQL build (i.e. 1007 or higher) will fix all known SQL
corruption bugs, but also enable new SQL Server I/O auditing features, such
as detection for stale read and lost writes, and perform consistency checks
on all pages read from the disk. Check all your database for corruption
before applying the hotfix. Then enable trace flags -T818 and -T806.
Lastly, the following articles contain more information about SQL I/O
requirements and how hardware problems may lead to corruption.
http://support.microsoft.com/kb/841776
http://support.microsoft.com/kb/826433
http://support.microsoft.com/kb/231619
http://www.microsoft.com/technet/pro...lIObasics.mspx
Adrian
"acs68" <adamst@.NOSPAMlaidley.qld.gov.au> wrote in message
news:eGuhUzPUFHA.2056@.tk2msftngp13.phx.gbl...
> Hi all,
> we have been using SQL7 for a number of years on a Win2K box without so
> much as one hiccup. Recently went out bought a new HP Server and SQL2000.
> Installed it all, moved all the databases - and everything seemed to be
> working fine.
> A couple of weeks ago we had a problem with our biggest database (about
> 1gb in size). Users were getting some errors from the app that uses it. I
> did a DBCC CHECKDB on that database and it was coming up with almost 1000
> inconsistencies etc etc. Tried Repair, to no avail and in the end just had
> to Restore form backup - lost about a half a days work - not critical for
> us.
> Spoke to a few DBA's who said that it sounded Hardware related. Spoke to
> our local IT support who we got the HP's from and they did a quick look
> and everything came up OK.
> A couple of days ago the same problem occurred. At a loss to explain what
> is happening, so I'm hoping a few of you may be able to help.
> One thing I did notice was that Write Cache was set on the server to 50%
> Read 50% Write. I have only now changed it to 100% and No Write caching.
> Could the above have caused it (50% Read 50% Write), or is it more than
> likely I could have further corruption ? We haven't , I believe, had any
> power outages or system crashes leading up to these corruptions.
> Any help you could give me would be greatly appreciated.
> cheers,
> Adam
>
|||Thanks for that advice Adrian, will look into it now.
cheers,
Adam
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:Wp-dnacXw-zo4-TfRVn-3A@.rogers.com...
> Adam,
> While it's quite possible that you are hitting some SQL bug which corrupts
> your database, it is far more likely that you may have some hardware or
> driver related problem on that server. I would advise you to install the
> latest SQL hotfix and update all your firmware and drivers. If you have
> enabled /PAE in BOOT.INI then apply the PAE fix Q838765. Also review your
> event logs in detail for ANY hardware-related errors and warnings. Use
> SQLIOSTRESS to try to flush out I/O problems.
> Going to the latest SQL build (i.e. 1007 or higher) will fix all known SQL
> corruption bugs, but also enable new SQL Server I/O auditing features,
> such as detection for stale read and lost writes, and perform consistency
> checks on all pages read from the disk. Check all your database for
> corruption before applying the hotfix. Then enable trace flags -T818
> and -T806.
> Lastly, the following articles contain more information about SQL I/O
> requirements and how hardware problems may lead to corruption.
> http://support.microsoft.com/kb/841776
> http://support.microsoft.com/kb/826433
> http://support.microsoft.com/kb/231619
> http://www.microsoft.com/technet/pro...lIObasics.mspx
> Adrian
>
>
> "acs68" <adamst@.NOSPAMlaidley.qld.gov.au> wrote in message
> news:eGuhUzPUFHA.2056@.tk2msftngp13.phx.gbl...
>
Corruption Problem- need some advice
we have been using SQL7 for a number of years on a Win2K box without so much
as one hiccup. Recently went out bought a new HP Server and SQL2000.
Installed it all, moved all the databases - and everything seemed to be
working fine.
A couple of weeks ago we had a problem with our biggest database (about 1gb
in size). Users were getting some errors from the app that uses it. I did a
DBCC CHECKDB on that database and it was coming up with almost 1000
inconsistencies etc etc. Tried Repair, to no avail and in the end just had
to Restore form backup - lost about a half a days work - not critical for
us.
Spoke to a few DBA's who said that it sounded Hardware related. Spoke to our
local IT support who we got the HP's from and they did a quick look and
everything came up OK.
A couple of days ago the same problem occurred. At a loss to explain what is
happening, so I'm hoping a few of you may be able to help.
One thing I did notice was that Write Cache was set on the server to 50%
Read 50% Write. I have only now changed it to 100% and No Write caching.
Could the above have caused it (50% Read 50% Write), or is it more than
likely I could have further corruption ? We haven't , I believe, had any
power outages or system crashes leading up to these corruptions.
Any help you could give me would be greatly appreciated.
cheers,
AdamAdam,
While it's quite possible that you are hitting some SQL bug which corrupts
your database, it is far more likely that you may have some hardware or
driver related problem on that server. I would advise you to install the
latest SQL hotfix and update all your firmware and drivers. If you have
enabled /PAE in BOOT.INI then apply the PAE fix Q838765. Also review your
event logs in detail for ANY hardware-related errors and warnings. Use
SQLIOSTRESS to try to flush out I/O problems.
Going to the latest SQL build (i.e. 1007 or higher) will fix all known SQL
corruption bugs, but also enable new SQL Server I/O auditing features, such
as detection for stale read and lost writes, and perform consistency checks
on all pages read from the disk. Check all your database for corruption
before applying the hotfix. Then enable trace flags -T818 and -T806.
Lastly, the following articles contain more information about SQL I/O
requirements and how hardware problems may lead to corruption.
http://support.microsoft.com/kb/841776
http://support.microsoft.com/kb/826433
http://support.microsoft.com/kb/231619
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
Adrian
"acs68" <adamst@.NOSPAMlaidley.qld.gov.au> wrote in message
news:eGuhUzPUFHA.2056@.tk2msftngp13.phx.gbl...
> Hi all,
> we have been using SQL7 for a number of years on a Win2K box without so
> much as one hiccup. Recently went out bought a new HP Server and SQL2000.
> Installed it all, moved all the databases - and everything seemed to be
> working fine.
> A couple of weeks ago we had a problem with our biggest database (about
> 1gb in size). Users were getting some errors from the app that uses it. I
> did a DBCC CHECKDB on that database and it was coming up with almost 1000
> inconsistencies etc etc. Tried Repair, to no avail and in the end just had
> to Restore form backup - lost about a half a days work - not critical for
> us.
> Spoke to a few DBA's who said that it sounded Hardware related. Spoke to
> our local IT support who we got the HP's from and they did a quick look
> and everything came up OK.
> A couple of days ago the same problem occurred. At a loss to explain what
> is happening, so I'm hoping a few of you may be able to help.
> One thing I did notice was that Write Cache was set on the server to 50%
> Read 50% Write. I have only now changed it to 100% and No Write caching.
> Could the above have caused it (50% Read 50% Write), or is it more than
> likely I could have further corruption ? We haven't , I believe, had any
> power outages or system crashes leading up to these corruptions.
> Any help you could give me would be greatly appreciated.
> cheers,
> Adam
>|||Thanks for that advice Adrian, will look into it now.
cheers,
Adam
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:Wp-dnacXw-zo4-TfRVn-3A@.rogers.com...
> Adam,
> While it's quite possible that you are hitting some SQL bug which corrupts
> your database, it is far more likely that you may have some hardware or
> driver related problem on that server. I would advise you to install the
> latest SQL hotfix and update all your firmware and drivers. If you have
> enabled /PAE in BOOT.INI then apply the PAE fix Q838765. Also review your
> event logs in detail for ANY hardware-related errors and warnings. Use
> SQLIOSTRESS to try to flush out I/O problems.
> Going to the latest SQL build (i.e. 1007 or higher) will fix all known SQL
> corruption bugs, but also enable new SQL Server I/O auditing features,
> such as detection for stale read and lost writes, and perform consistency
> checks on all pages read from the disk. Check all your database for
> corruption before applying the hotfix. Then enable trace flags -T818
> and -T806.
> Lastly, the following articles contain more information about SQL I/O
> requirements and how hardware problems may lead to corruption.
> http://support.microsoft.com/kb/841776
> http://support.microsoft.com/kb/826433
> http://support.microsoft.com/kb/231619
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
> Adrian
>
>
> "acs68" <adamst@.NOSPAMlaidley.qld.gov.au> wrote in message
> news:eGuhUzPUFHA.2056@.tk2msftngp13.phx.gbl...
>> Hi all,
>> we have been using SQL7 for a number of years on a Win2K box without so
>> much as one hiccup. Recently went out bought a new HP Server and SQL2000.
>> Installed it all, moved all the databases - and everything seemed to be
>> working fine.
>> A couple of weeks ago we had a problem with our biggest database (about
>> 1gb in size). Users were getting some errors from the app that uses it. I
>> did a DBCC CHECKDB on that database and it was coming up with almost 1000
>> inconsistencies etc etc. Tried Repair, to no avail and in the end just
>> had to Restore form backup - lost about a half a days work - not critical
>> for us.
>> Spoke to a few DBA's who said that it sounded Hardware related. Spoke to
>> our local IT support who we got the HP's from and they did a quick look
>> and everything came up OK.
>> A couple of days ago the same problem occurred. At a loss to explain what
>> is happening, so I'm hoping a few of you may be able to help.
>> One thing I did notice was that Write Cache was set on the server to 50%
>> Read 50% Write. I have only now changed it to 100% and No Write caching.
>> Could the above have caused it (50% Read 50% Write), or is it more than
>> likely I could have further corruption ? We haven't , I believe, had any
>> power outages or system crashes leading up to these corruptions.
>> Any help you could give me would be greatly appreciated.
>> cheers,
>> Adam
>
corruption of database maintenance wizard
the screen that holds the settings is corrupted
I can no longer define how many backups have to stay in the folder
(disk backup)
I can set the number but the listbox after that stays empty so I can
not set "hours" or "days"
the job itself doesn't work neither
the existing jobs keep happening but are no longer visible in the
enterprise manager
can I solve this some way?
maybe with queries?
I did try to use the "new" sql 2005 console for my 2k servers
could this be related?
thnxSQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in
what they can do etc. The 2005 tool is not meant to edit 2000 plans. You
may have to redo them using 2000 EM since there is no telling what might
have changed.
--
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.3b897d6207852634.36062@.yahoo.com...
> when I try to add a job I am unable to use the wizard
> the screen that holds the settings is corrupted
> I can no longer define how many backups have to stay in the folder (disk
> backup)
> I can set the number but the listbox after that stays empty so I can not
> set "hours" or "days"
> the job itself doesn't work neither
> the existing jobs keep happening but are no longer visible in the
> enterprise manager
> can I solve this some way?
> maybe with queries?
> I did try to use the "new" sql 2005 console for my 2k servers
> could this be related?
> thnx
>|||> SQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in
> what they can do etc. The 2005 tool is not meant to edit 2000 plans. You
> may have to redo them using 2000 EM since there is no telling what might have
> changed.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.3b897d6207852634.36062@.yahoo.com...
>> when I try to add a job I am unable to use the wizard
>> the screen that holds the settings is corrupted
>> I can no longer define how many backups have to stay in the folder (disk
>> backup)
>> I can set the number but the listbox after that stays empty so I can not
>> set "hours" or "days"
>> the job itself doesn't work neither
>> the existing jobs keep happening but are no longer visible in the
>> enterprise manager
>> can I solve this some way?
>> maybe with queries?
>> I did try to use the "new" sql 2005 console for my 2k servers
>> could this be related?
>> thnx
>>
I didn't try to change anything using the 2k5 VS tool
but I can't change it using the 2k enterprise manager anymore
since the wizard got corrupted somehow
I am not sure if it is related
my question is how to repair it without interrupting the server
functionality (too much)
grtz|||Since I have no way to know what is corrupted all I can say is to delete any
that you suspect are corrupt and rebuild them.
--
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.42317d62800a030b.36062@.yahoo.com...
>> SQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in
>> what they can do etc. The 2005 tool is not meant to edit 2000 plans.
>> You may have to redo them using 2000 EM since there is no telling what
>> might have changed.
>> --
>> Andrew J. Kelly SQL MVP
>> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
>> news:mn.3b897d6207852634.36062@.yahoo.com...
>> when I try to add a job I am unable to use the wizard
>> the screen that holds the settings is corrupted
>> I can no longer define how many backups have to stay in the folder (disk
>> backup)
>> I can set the number but the listbox after that stays empty so I can not
>> set "hours" or "days"
>> the job itself doesn't work neither
>> the existing jobs keep happening but are no longer visible in the
>> enterprise manager
>> can I solve this some way?
>> maybe with queries?
>> I did try to use the "new" sql 2005 console for my 2k servers
>> could this be related?
>> thnx
>>
> I didn't try to change anything using the 2k5 VS tool
> but I can't change it using the 2k enterprise manager anymore
> since the wizard got corrupted somehow
> I am not sure if it is related
> my question is how to repair it without interrupting the server
> functionality (too much)
> grtz
>|||> Since I have no way to know what is corrupted all I can say is to delete any
> that you suspect are corrupt and rebuild them.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.42317d62800a030b.36062@.yahoo.com...
>>
>> I didn't try to change anything using the 2k5 VS tool
>> but I can't change it using the 2k enterprise manager anymore
>> since the wizard got corrupted somehow
>> I am not sure if it is related
>> my question is how to repair it without interrupting the server
>> functionality (too much)
>> grtz
>>
I'd like to but I can't
the interface doesn't show me any jobs
but they do still work
I just cannot add any new ones because the wizard is broken somehow
grtz|||You should still be able to create a new maintenance plan and add what ever
you want there. They don't have to all be in the same plan.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.521c7d6216230948.36062@.yahoo.com...
>> Since I have no way to know what is corrupted all I can say is to delete
>> any that you suspect are corrupt and rebuild them.
>> --
>> Andrew J. Kelly SQL MVP
>> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
>> news:mn.42317d62800a030b.36062@.yahoo.com...
>>
>> I didn't try to change anything using the 2k5 VS tool
>> but I can't change it using the 2k enterprise manager anymore
>> since the wizard got corrupted somehow
>> I am not sure if it is related
>> my question is how to repair it without interrupting the server
>> functionality (too much)
>> grtz
>>
> I'd like to but I can't
> the interface doesn't show me any jobs
> but they do still work
> I just cannot add any new ones because the wizard is broken somehow
> grtz
>|||> You should still be able to create a new maintenance plan and add what ever
> you want there. They don't have to all be in the same plan.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.521c7d6216230948.36062@.yahoo.com...
>>
>> I'd like to but I can't
>> the interface doesn't show me any jobs
>> but they do still work
>> I just cannot add any new ones because the wizard is broken somehow
>> grtz
>>
no I cannot,
for some reason the wizard doesn't allow me to set a value for how many
files I'd like to keep in the backup folder
I can set a number but not the type of value after that
I already tried to add a new job anyway but it keeps failing
since I have no idea how to fix the wizard I thought I'd give the
experts a try to tell me why,how and where the wizard might fail
and how to repair it's behaviour
perhaps thru sql?
grtz|||Without seeing what you have I really have no idea how to fix it. I rarely
advocate using the maintenance plan wizard at all for so many reasons, this
being just one. Anything you can do with he wizard can be done fairly
easily with simple tsql commands and a normal scheduled job. But you can use
the same utility that the wizard uses to execute these tasks and you don't
need to use the gui to do it. Create a new scheduled job and call the
sqlmaint utility with the appropriate parameters to do what you want done.
See "sqlmaint utility" in BooksOnLine for the details.
--
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.53927d6233044d14.36062@.yahoo.com...
>> You should still be able to create a new maintenance plan and add what
>> ever you want there. They don't have to all be in the same plan.
>> --
>> Andrew J. Kelly SQL MVP
>> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
>> news:mn.521c7d6216230948.36062@.yahoo.com...
>>
>> I'd like to but I can't
>> the interface doesn't show me any jobs
>> but they do still work
>> I just cannot add any new ones because the wizard is broken somehow
>> grtz
>>
> no I cannot,
> for some reason the wizard doesn't allow me to set a value for how many
> files I'd like to keep in the backup folder
> I can set a number but not the type of value after that
> I already tried to add a new job anyway but it keeps failing
> since I have no idea how to fix the wizard I thought I'd give the experts
> a try to tell me why,how and where the wizard might fail
> and how to repair it's behaviour
> perhaps thru sql?
> grtz
>
corruption of database maintenance wizard
the screen that holds the settings is corrupted
I can no longer define how many backups have to stay in the folder
(disk backup)
I can set the number but the listbox after that stays empty so I can
not set "hours" or "days"
the job itself doesn't work neither
the existing jobs keep happening but are no longer visible in the
enterprise manager
can I solve this some way?
maybe with queries?
I did try to use the "new" sql 2005 console for my 2k servers
could this be related?
thnx
SQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in
what they can do etc. The 2005 tool is not meant to edit 2000 plans. You
may have to redo them using 2000 EM since there is no telling what might
have changed.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.3b897d6207852634.36062@.yahoo.com...
> when I try to add a job I am unable to use the wizard
> the screen that holds the settings is corrupted
> I can no longer define how many backups have to stay in the folder (disk
> backup)
> I can set the number but the listbox after that stays empty so I can not
> set "hours" or "days"
> the job itself doesn't work neither
> the existing jobs keep happening but are no longer visible in the
> enterprise manager
> can I solve this some way?
> maybe with queries?
> I did try to use the "new" sql 2005 console for my 2k servers
> could this be related?
> thnx
>
|||> SQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in[vbcol=seagreen]
> what they can do etc. The 2005 tool is not meant to edit 2000 plans. You
> may have to redo them using 2000 EM since there is no telling what might have
> changed.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.3b897d6207852634.36062@.yahoo.com...
I didn't try to change anything using the 2k5 VS tool
but I can't change it using the 2k enterprise manager anymore
since the wizard got corrupted somehow
I am not sure if it is related
my question is how to repair it without interrupting the server
functionality (too much)
grtz
|||Since I have no way to know what is corrupted all I can say is to delete any
that you suspect are corrupt and rebuild them.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.42317d62800a030b.36062@.yahoo.com...
> I didn't try to change anything using the 2k5 VS tool
> but I can't change it using the 2k enterprise manager anymore
> since the wizard got corrupted somehow
> I am not sure if it is related
> my question is how to repair it without interrupting the server
> functionality (too much)
> grtz
>
|||> Since I have no way to know what is corrupted all I can say is to delete any[vbcol=seagreen]
> that you suspect are corrupt and rebuild them.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.42317d62800a030b.36062@.yahoo.com...
I'd like to but I can't
the interface doesn't show me any jobs
but they do still work
I just cannot add any new ones because the wizard is broken somehow
grtz
|||You should still be able to create a new maintenance plan and add what ever
you want there. They don't have to all be in the same plan.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.521c7d6216230948.36062@.yahoo.com...
> I'd like to but I can't
> the interface doesn't show me any jobs
> but they do still work
> I just cannot add any new ones because the wizard is broken somehow
> grtz
>
|||> You should still be able to create a new maintenance plan and add what ever[vbcol=seagreen]
> you want there. They don't have to all be in the same plan.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.521c7d6216230948.36062@.yahoo.com...
no I cannot,
for some reason the wizard doesn't allow me to set a value for how many
files I'd like to keep in the backup folder
I can set a number but not the type of value after that
I already tried to add a new job anyway but it keeps failing
since I have no idea how to fix the wizard I thought I'd give the
experts a try to tell me why,how and where the wizard might fail
and how to repair it's behaviour
perhaps thru sql?
grtz
|||Without seeing what you have I really have no idea how to fix it. I rarely
advocate using the maintenance plan wizard at all for so many reasons, this
being just one. Anything you can do with he wizard can be done fairly
easily with simple tsql commands and a normal scheduled job. But you can use
the same utility that the wizard uses to execute these tasks and you don't
need to use the gui to do it. Create a new scheduled job and call the
sqlmaint utility with the appropriate parameters to do what you want done.
See "sqlmaint utility" in BooksOnLine for the details.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.53927d6233044d14.36062@.yahoo.com...
> no I cannot,
> for some reason the wizard doesn't allow me to set a value for how many
> files I'd like to keep in the backup folder
> I can set a number but not the type of value after that
> I already tried to add a new job anyway but it keeps failing
> since I have no idea how to fix the wizard I thought I'd give the experts
> a try to tell me why,how and where the wizard might fail
> and how to repair it's behaviour
> perhaps thru sql?
> grtz
>
corruption of database maintenance wizard
the screen that holds the settings is corrupted
I can no longer define how many backups have to stay in the folder
(disk backup)
I can set the number but the listbox after that stays empty so I can
not set "hours" or "days"
the job itself doesn't work neither
the existing jobs keep happening but are no longer visible in the
enterprise manager
can I solve this some way?
maybe with queries?
I did try to use the "new" sql 2005 console for my 2k servers
could this be related?
thnxSQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in
what they can do etc. The 2005 tool is not meant to edit 2000 plans. You
may have to redo them using 2000 EM since there is no telling what might
have changed.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.3b897d6207852634.36062@.yahoo.com...
> when I try to add a job I am unable to use the wizard
> the screen that holds the settings is corrupted
> I can no longer define how many backups have to stay in the folder (disk
> backup)
> I can set the number but the listbox after that stays empty so I can not
> set "hours" or "days"
> the job itself doesn't work neither
> the existing jobs keep happening but are no longer visible in the
> enterprise manager
> can I solve this some way?
> maybe with queries?
> I did try to use the "new" sql 2005 console for my 2k servers
> could this be related?
> thnx
>|||> SQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in[vbcol=seagreen]
> what they can do etc. The 2005 tool is not meant to edit 2000 plans. You
> may have to redo them using 2000 EM since there is no telling what might h
ave
> changed.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.3b897d6207852634.36062@.yahoo.com...
I didn't try to change anything using the 2k5 VS tool
but I can't change it using the 2k enterprise manager anymore
since the wizard got corrupted somehow
I am not sure if it is related
my question is how to repair it without interrupting the server
functionality (too much)
grtz|||Since I have no way to know what is corrupted all I can say is to delete any
that you suspect are corrupt and rebuild them.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.42317d62800a030b.36062@.yahoo.com...
> I didn't try to change anything using the 2k5 VS tool
> but I can't change it using the 2k enterprise manager anymore
> since the wizard got corrupted somehow
> I am not sure if it is related
> my question is how to repair it without interrupting the server
> functionality (too much)
> grtz
>|||> Since I have no way to know what is corrupted all I can say is to delete any[vbcol=seagree
n]
> that you suspect are corrupt and rebuild them.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.42317d62800a030b.36062@.yahoo.com...
I'd like to but I can't
the interface doesn't show me any jobs
but they do still work
I just cannot add any new ones because the wizard is broken somehow
grtz|||You should still be able to create a new maintenance plan and add what ever
you want there. They don't have to all be in the same plan.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.521c7d6216230948.36062@.yahoo.com...
> I'd like to but I can't
> the interface doesn't show me any jobs
> but they do still work
> I just cannot add any new ones because the wizard is broken somehow
> grtz
>|||> You should still be able to create a new maintenance plan and add what ever[vbcol=seagreen
]
> you want there. They don't have to all be in the same plan.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.521c7d6216230948.36062@.yahoo.com...
no I cannot,
for some reason the wizard doesn't allow me to set a value for how many
files I'd like to keep in the backup folder
I can set a number but not the type of value after that
I already tried to add a new job anyway but it keeps failing
since I have no idea how to fix the wizard I thought I'd give the
experts a try to tell me why,how and where the wizard might fail
and how to repair it's behaviour
perhaps thru sql?
grtz|||Without seeing what you have I really have no idea how to fix it. I rarely
advocate using the maintenance plan wizard at all for so many reasons, this
being just one. Anything you can do with he wizard can be done fairly
easily with simple tsql commands and a normal scheduled job. But you can use
the same utility that the wizard uses to execute these tasks and you don't
need to use the gui to do it. Create a new scheduled job and call the
sqlmaint utility with the appropriate parameters to do what you want done.
See "sqlmaint utility" in BooksOnLine for the details.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.53927d6233044d14.36062@.yahoo.com...
> no I cannot,
> for some reason the wizard doesn't allow me to set a value for how many
> files I'd like to keep in the backup folder
> I can set a number but not the type of value after that
> I already tried to add a new job anyway but it keeps failing
> since I have no idea how to fix the wizard I thought I'd give the experts
> a try to tell me why,how and where the wizard might fail
> and how to repair it's behaviour
> perhaps thru sql?
> grtz
>
Corruption of backup file on remote server
Dear all,
What I want to do is to backup my database through the SQL script, when the backup is successful, the .bak file is saved in my local harddisk. After that, I used the XYRunProc to execute a "copy" command to copy the .bak file to a remote server.
However, when I want to restore the database using the .bak on the remote server, I found that the .bak is corrupted. This problem does not exist if the file is copied to the remote server manually (click copy on local server and click paste on remote server).
Do anyone know what's the problem of this? This really made me very frustrated. Hope someone can help me, thank you very much!
Regards,
Strike
Hi Strike,
XYRunProc is an extended stored procedure written by someone outside of Microsoft. I couldn't even begin to tell you how it works or why it might be causing problems when copying files. Since a manual copy doesn't seem to affect the .bak file, it's clearly something about how XYRunProc is handling it.
I would suggest you contact the author of the xProc to determine what might be happening during the file copy.
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
Corruption
Are SQL server databases prone to corruption?
MikeNot in 7.0 or 2000. Corruption these days is usually due to faulty hardware
or power outages, both of which can be mostly avoided with the right
configuration.
--
Andrew J. Kelly
SQL Server MVP
"Mike Tremendous" <noone@.hotmail.com> wrote in message
news:%23I3aZBxrDHA.2304@.TK2MSFTNGP12.phx.gbl...
> Hi. Quick question:
> Are SQL server databases prone to corruption?
> Mike
>|||> > Hi. Quick question:
> > Are SQL server databases prone to corruption?
> Not in 7.0 or 2000. Corruption these days is usually due to faulty
hardware
> or power outages, both of which can be mostly avoided with the right
> configuration.
What about with so-called 'abnormal' use? Eg:
- What if there are clients not disconneting cleanly and leaving
transactions open?
- How about creating foreign keys and the like whilst other users are
connected?
- What about executing a huge transactions that effects, say, 10,000,000
rows, and then rolling it back?
- What about restarting the SQL Server service with clients connected and
transactions open?
Can it cope with these scenarios?
Mike|||Yes these are essentially non-issues when it comes to corrupting the
database. Any time a user is disconnected the server will automatically
roll back any open trans. Creating keys and huge trans are all Atomic
operations and the only issue is user performance not stability. Even
restarting a server should not be an issue from a sql server standpoint as
when it restarts it will automatically roll back any uncommitted trans
before it allows new ones in. I wouldn't recommend restarting a server with
users in it for general purposes but SQL Server wouldn't be much of an
enterprise db if it didn't handle the issues you pose correctly.
--
Andrew J. Kelly
SQL Server MVP
"Mike Tremendous" <noone@.hotmail.com> wrote in message
news:OLKPgZzrDHA.1740@.TK2MSFTNGP12.phx.gbl...
> > > Hi. Quick question:
> > > Are SQL server databases prone to corruption?
> >
> > Not in 7.0 or 2000. Corruption these days is usually due to faulty
> hardware
> > or power outages, both of which can be mostly avoided with the right
> > configuration.
> What about with so-called 'abnormal' use? Eg:
> - What if there are clients not disconneting cleanly and leaving
> transactions open?
> - How about creating foreign keys and the like whilst other users are
> connected?
> - What about executing a huge transactions that effects, say, 10,000,000
> rows, and then rolling it back?
> - What about restarting the SQL Server service with clients connected and
> transactions open?
> Can it cope with these scenarios?
> Mike
>|||> Yes these are essentially non-issues when it comes to corrupting the
> database. Any time a user is disconnected the server will automatically
> roll back any open trans. Creating keys and huge trans are all Atomic
> operations and the only issue is user performance not stability. Even
> restarting a server should not be an issue from a sql server standpoint as
> when it restarts it will automatically roll back any uncommitted trans
> before it allows new ones in. I wouldn't recommend restarting a server
with
> users in it for general purposes but SQL Server wouldn't be much of an
> enterprise db if it didn't handle the issues you pose correctly.
Thanks for the advice.
Mike