Prev: Install SQL2008 Std edtn x64
Next: Enable Full Text Search
From: Kalen Delaney on 27 Nov 2009 13:12
Hi Rubens

Why are you stunned? You never mentioned you were looking elsewhere for
help.

Are you assuming everybody knew exactly how competent you are just from the
contents of this post? Have you read some of the other posts here to see
what people expect from this forum?

We get posts that say "EMERGENCY... PLEASE ANSWER IMMEDIATELY... My
production database is marked suspect and nobody can use it. WHAT DO I DO?"

Saying that you're stunned implies you expected more from someone, and that
could be construed as criticism. I suggest you try NOT to criticize the
people who are donating their free time and volunteering to help you on this
forum. I understand you might not want to appear less competent than you
think you are, but criticizing Kevin, who has been providing high quality
volunteer help for years, doesn't help your image.
--
HTH
Kalen
----------------------------------------
Kalen Delaney
SQL Server MVP
www.SQLServerInternals.com

"Rubens" <rubensrose(a)hotmail.com> wrote in message
news:C598299C-72D1-4B15-A565-4CDA17ED5189(a)microsoft.com...
> I'm a little stunned that you'd make the assumption that this was all I
> was doing. I already had a call into Microsoft when I posted this and was
> waiting for a call back, so I was looking to this group to provide me a
> little direction as I was researching the problem on my own.
>
> Thanks for your help Kevin.
>
> Rubens
>
> "TheSQLGuru" <kgboles(a)earthlink.net> wrote in message
> news:4ISdnWvcFrOt-JbWnZ2dnUVZ_uednZ2d(a)earthlink.com...
>> Gotta say I am pretty stunned that you have failing backups and a
>> potentially corrupted system on a 1.7TB OLTP system and you are hunting
>> and pecking here on a forum for help? This should be zooming up the food
>> chain at Microsoft customer support...
>>
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>>
>> "Rubens" <rubensrose(a)hotmail.com> wrote in message
>> news:0D1604E3-BB25-488E-8251-4BFF84C5A257(a)microsoft.com...
>>>I have a rather concerning issue on our OLTP system for our largest
>>>database (1.7 TB's). On Friday (when I was on vacation of course), we
>>>had a power outage and the cluster failed. Everything was brought back
>>>online from the Network guys, and then our team of DBA's took over with
>>>making sure SQL was ok using the documentation we have. Since then, the
>>>log backups for the above database began to fail, but it still appears to
>>>be writing the log files. We do weekly full backups, followed by daily
>>>differentials. My hope was that after the full backup ran, everything
>>>would be fine with the log backups. Nope, they are still failing with
>>>the error message below...
>>>
>>> Processed 127550 pages for database 'Focus', file 'Focus2000_Log' on
>>> file 1. [SQLSTATE 01000] (Message 4035) Processed 0 pages for database
>>> 'Focus', file 'Focus2000_Log3' on file 1. [SQLSTATE 01000] (Message
>>> 4035) Cannot insert duplicate key row in object 'sys.syscommittab' with
>>> unique index 'si_xdes_id'. [SQLSTATE 23000] (Error 2601) Failed to
>>> flush the commit table to disk in dbid 7 due to error 2601. Check the
>>> errorlog for more information. [SQLSTATE 42000] (Error 3999) The
>>> statement has been terminated. [SQLSTATE 01000] (Error 3621). The step
>>> failed.
>>>
>>> I was hoping that the weekend full backups would reset the database and
>>> then the log backups would run fine after. NOPE. Still having the same
>>> issue. And interestingly, or index rebuild job failed with the same
>>> error message for this database.
>>>
>>> SQL 2008 SP1, Enterprise Edition, active-active-active cluster on
>>> Windows 2003 R2 x64 SP2
>>>
>>> Can someone offer any advice?
>>>
>>> Thanks,
>>> Rubens
>>
>>
From: Rubens on 27 Nov 2009 16:42
Hi Kalen,

As you can imagine, it was a rather urgent situation and yes, I did fail to
mention that I had contacted Microsoft first.

My original post was a question for a serious problem and the reply I
received was not a constructive one. That was what I found surprising.

I'd like to ask you this. What "help" did Kevin offer in his post other
than to criticize me for posting such a critical issue to this newsgroup?
His reply only indicated he was stunned I came here.

If anything, the fact that I posted here indicates the respect I have for
the level of expertise I've received in the past, and not just from
yourself, but other MVP's such as Kevin. I have and still do consider you
all a very valuable resource, and I have a lot of respect for your posts.

When you have something as critical as what I posted, it's all-hands-on-deck
as I am sure you are fully aware. All I was trying to do was make use of
all the resources available to me to educate myself on the problem so I
could hit the ground running.

I obviously did not have the technical expertise to resolve this on my own,
which is again why I reached out. And if you read every post I've ever
made, you will see just how thankful I have been to the community for their
assistance.

Thanks,
Rubens


"Kalen Delaney" <please_reply_on_newsgroups(a)domain.com> wrote in message
news:59CC9286-A0BD-4CE1-A185-B65D818AE01D(a)microsoft.com...
> Hi Rubens
>
> Why are you stunned? You never mentioned you were looking elsewhere for
> help.
>
> Are you assuming everybody knew exactly how competent you are just from
> the contents of this post? Have you read some of the other posts here to
> see what people expect from this forum?
>
> We get posts that say "EMERGENCY... PLEASE ANSWER IMMEDIATELY... My
> production database is marked suspect and nobody can use it. WHAT DO I
> DO?"
>
> Saying that you're stunned implies you expected more from someone, and
> that could be construed as criticism. I suggest you try NOT to criticize
> the people who are donating their free time and volunteering to help you
> on this forum. I understand you might not want to appear less competent
> than you think you are, but criticizing Kevin, who has been providing high
> quality volunteer help for years, doesn't help your image.
> --
> HTH
> Kalen
> ----------------------------------------
> Kalen Delaney
> SQL Server MVP
> www.SQLServerInternals.com
>
> "Rubens" <rubensrose(a)hotmail.com> wrote in message
> news:C598299C-72D1-4B15-A565-4CDA17ED5189(a)microsoft.com...
>> I'm a little stunned that you'd make the assumption that this was all I
>> was doing. I already had a call into Microsoft when I posted this and
>> was waiting for a call back, so I was looking to this group to provide me
>> a little direction as I was researching the problem on my own.
>>
>> Thanks for your help Kevin.
>>
>> Rubens
>>
>> "TheSQLGuru" <kgboles(a)earthlink.net> wrote in message
>> news:4ISdnWvcFrOt-JbWnZ2dnUVZ_uednZ2d(a)earthlink.com...
>>> Gotta say I am pretty stunned that you have failing backups and a
>>> potentially corrupted system on a 1.7TB OLTP system and you are hunting
>>> and pecking here on a forum for help? This should be zooming up the
>>> food chain at Microsoft customer support...
>>>
>>> --
>>> Kevin G. Boles
>>> Indicium Resources, Inc.
>>> SQL Server MVP
>>> kgboles a earthlink dt net
>>>
>>>
>>> "Rubens" <rubensrose(a)hotmail.com> wrote in message
>>> news:0D1604E3-BB25-488E-8251-4BFF84C5A257(a)microsoft.com...
>>>>I have a rather concerning issue on our OLTP system for our largest
>>>>database (1.7 TB's). On Friday (when I was on vacation of course), we
>>>>had a power outage and the cluster failed. Everything was brought back
>>>>online from the Network guys, and then our team of DBA's took over with
>>>>making sure SQL was ok using the documentation we have. Since then, the
>>>>log backups for the above database began to fail, but it still appears
>>>>to be writing the log files. We do weekly full backups, followed by
>>>>daily differentials. My hope was that after the full backup ran,
>>>>everything would be fine with the log backups. Nope, they are still
>>>>failing with the error message below...
>>>>
>>>> Processed 127550 pages for database 'Focus', file 'Focus2000_Log' on
>>>> file 1. [SQLSTATE 01000] (Message 4035) Processed 0 pages for database
>>>> 'Focus', file 'Focus2000_Log3' on file 1. [SQLSTATE 01000] (Message
>>>> 4035) Cannot insert duplicate key row in object 'sys.syscommittab' with
>>>> unique index 'si_xdes_id'. [SQLSTATE 23000] (Error 2601) Failed to
>>>> flush the commit table to disk in dbid 7 due to error 2601. Check the
>>>> errorlog for more information. [SQLSTATE 42000] (Error 3999) The
>>>> statement has been terminated. [SQLSTATE 01000] (Error 3621). The step
>>>> failed.
>>>>
>>>> I was hoping that the weekend full backups would reset the database and
>>>> then the log backups would run fine after. NOPE. Still having the
>>>> same issue. And interestingly, or index rebuild job failed with the
>>>> same error message for this database.
>>>>
>>>> SQL 2008 SP1, Enterprise Edition, active-active-active cluster on
>>>> Windows 2003 R2 x64 SP2
>>>>
>>>> Can someone offer any advice?
>>>>
>>>> Thanks,
>>>> Rubens
>>>
>>>
From: TheSQLGuru on 28 Nov 2009 11:42
There have been many examples of people who have wasted a LOT of time
looking for help on forums for a production outage when getting MS support
(or a qualified consultant) on board immediately was by far their best
option. I recommended that as your best option since you failed to mention
that you were already in the queue with MS support.

I could have also asked other questions but they would have all been related
to what could/should have been done (had you been doing consistency checks,
had you been doing test restores of your backups to make sure they were
viable, etc), but I did not because they were not relevant or helpful to
getting you back online. I could also question if appropriate measures were
in place on the hardware and infrastructure side such as battery backups for
caches and systems as a whole and why the system wasn't shut down gracefully
when the power went out. Hopefully if all of those things were not being
done you can now put them into place once you get back online.

Best of luck with the recovery.

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"Rubens" <rubensrose(a)hotmail.com> wrote in message
news:C598299C-72D1-4B15-A565-4CDA17ED5189(a)microsoft.com...
> I'm a little stunned that you'd make the assumption that this was all I
> was doing. I already had a call into Microsoft when I posted this and was
> waiting for a call back, so I was looking to this group to provide me a
> little direction as I was researching the problem on my own.
>
> Thanks for your help Kevin.
>
> Rubens
>
> "TheSQLGuru" <kgboles(a)earthlink.net> wrote in message
> news:4ISdnWvcFrOt-JbWnZ2dnUVZ_uednZ2d(a)earthlink.com...
>> Gotta say I am pretty stunned that you have failing backups and a
>> potentially corrupted system on a 1.7TB OLTP system and you are hunting
>> and pecking here on a forum for help? This should be zooming up the food
>> chain at Microsoft customer support...
>>
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>>
>> "Rubens" <rubensrose(a)hotmail.com> wrote in message
>> news:0D1604E3-BB25-488E-8251-4BFF84C5A257(a)microsoft.com...
>>>I have a rather concerning issue on our OLTP system for our largest
>>>database (1.7 TB's). On Friday (when I was on vacation of course), we
>>>had a power outage and the cluster failed. Everything was brought back
>>>online from the Network guys, and then our team of DBA's took over with
>>>making sure SQL was ok using the documentation we have. Since then, the
>>>log backups for the above database began to fail, but it still appears to
>>>be writing the log files. We do weekly full backups, followed by daily
>>>differentials. My hope was that after the full backup ran, everything
>>>would be fine with the log backups. Nope, they are still failing with
>>>the error message below...
>>>
>>> Processed 127550 pages for database 'Focus', file 'Focus2000_Log' on
>>> file 1. [SQLSTATE 01000] (Message 4035) Processed 0 pages for database
>>> 'Focus', file 'Focus2000_Log3' on file 1. [SQLSTATE 01000] (Message
>>> 4035) Cannot insert duplicate key row in object 'sys.syscommittab' with
>>> unique index 'si_xdes_id'. [SQLSTATE 23000] (Error 2601) Failed to
>>> flush the commit table to disk in dbid 7 due to error 2601. Check the
>>> errorlog for more information. [SQLSTATE 42000] (Error 3999) The
>>> statement has been terminated. [SQLSTATE 01000] (Error 3621). The step
>>> failed.
>>>
>>> I was hoping that the weekend full backups would reset the database and
>>> then the log backups would run fine after. NOPE. Still having the same
>>> issue. And interestingly, or index rebuild job failed with the same
>>> error message for this database.
>>>
>>> SQL 2008 SP1, Enterprise Edition, active-active-active cluster on
>>> Windows 2003 R2 x64 SP2
>>>
>>> Can someone offer any advice?
>>>
>>> Thanks,
>>> Rubens
>>
>>


From: Kalen Delaney on 28 Nov 2009 12:36
My only concern was you stating that you were 'stunned' at Kevin's
assumptions, as if he/we should know what else you had been doing.

--
HTH
Kalen
----------------------------------------
Kalen Delaney
SQL Server MVP
www.SQLServerInternals.com

"Rubens" <rubensrose(a)hotmail.com> wrote in message
news:9965416C-07B8-4EF7-AF6F-3F4FD20723A0(a)microsoft.com...
> Hi Kalen,
>
> As you can imagine, it was a rather urgent situation and yes, I did fail
> to mention that I had contacted Microsoft first.
>
> My original post was a question for a serious problem and the reply I
> received was not a constructive one. That was what I found surprising.
>
> I'd like to ask you this. What "help" did Kevin offer in his post other
> than to criticize me for posting such a critical issue to this newsgroup?
> His reply only indicated he was stunned I came here.
>
> If anything, the fact that I posted here indicates the respect I have for
> the level of expertise I've received in the past, and not just from
> yourself, but other MVP's such as Kevin. I have and still do consider you
> all a very valuable resource, and I have a lot of respect for your posts.
>
> When you have something as critical as what I posted, it's
> all-hands-on-deck as I am sure you are fully aware. All I was trying to
> do was make use of all the resources available to me to educate myself on
> the problem so I could hit the ground running.
>
> I obviously did not have the technical expertise to resolve this on my
> own, which is again why I reached out. And if you read every post I've
> ever made, you will see just how thankful I have been to the community for
> their assistance.
>
> Thanks,
> Rubens
>
>
> "Kalen Delaney" <please_reply_on_newsgroups(a)domain.com> wrote in message
> news:59CC9286-A0BD-4CE1-A185-B65D818AE01D(a)microsoft.com...
>> Hi Rubens
>>
>> Why are you stunned? You never mentioned you were looking elsewhere for
>> help.
>>
>> Are you assuming everybody knew exactly how competent you are just from
>> the contents of this post? Have you read some of the other posts here to
>> see what people expect from this forum?
>>
>> We get posts that say "EMERGENCY... PLEASE ANSWER IMMEDIATELY... My
>> production database is marked suspect and nobody can use it. WHAT DO I
>> DO?"
>>
>> Saying that you're stunned implies you expected more from someone, and
>> that could be construed as criticism. I suggest you try NOT to criticize
>> the people who are donating their free time and volunteering to help you
>> on this forum. I understand you might not want to appear less competent
>> than you think you are, but criticizing Kevin, who has been providing
>> high quality volunteer help for years, doesn't help your image.
>> --
>> HTH
>> Kalen
>> ----------------------------------------
>> Kalen Delaney
>> SQL Server MVP
>> www.SQLServerInternals.com
>>
>> "Rubens" <rubensrose(a)hotmail.com> wrote in message
>> news:C598299C-72D1-4B15-A565-4CDA17ED5189(a)microsoft.com...
>>> I'm a little stunned that you'd make the assumption that this was all I
>>> was doing. I already had a call into Microsoft when I posted this and
>>> was waiting for a call back, so I was looking to this group to provide
>>> me a little direction as I was researching the problem on my own.
>>>
>>> Thanks for your help Kevin.
>>>
>>> Rubens
>>>
>>> "TheSQLGuru" <kgboles(a)earthlink.net> wrote in message
>>> news:4ISdnWvcFrOt-JbWnZ2dnUVZ_uednZ2d(a)earthlink.com...
>>>> Gotta say I am pretty stunned that you have failing backups and a
>>>> potentially corrupted system on a 1.7TB OLTP system and you are hunting
>>>> and pecking here on a forum for help? This should be zooming up the
>>>> food chain at Microsoft customer support...
>>>>
>>>> --
>>>> Kevin G. Boles
>>>> Indicium Resources, Inc.
>>>> SQL Server MVP
>>>> kgboles a earthlink dt net
>>>>
>>>>
>>>> "Rubens" <rubensrose(a)hotmail.com> wrote in message
>>>> news:0D1604E3-BB25-488E-8251-4BFF84C5A257(a)microsoft.com...
>>>>>I have a rather concerning issue on our OLTP system for our largest
>>>>>database (1.7 TB's). On Friday (when I was on vacation of course), we
>>>>>had a power outage and the cluster failed. Everything was brought back
>>>>>online from the Network guys, and then our team of DBA's took over with
>>>>>making sure SQL was ok using the documentation we have. Since then,
>>>>>the log backups for the above database began to fail, but it still
>>>>>appears to be writing the log files. We do weekly full backups,
>>>>>followed by daily differentials. My hope was that after the full
>>>>>backup ran, everything would be fine with the log backups. Nope, they
>>>>>are still failing with the error message below...
>>>>>
>>>>> Processed 127550 pages for database 'Focus', file 'Focus2000_Log' on
>>>>> file 1. [SQLSTATE 01000] (Message 4035) Processed 0 pages for
>>>>> database 'Focus', file 'Focus2000_Log3' on file 1. [SQLSTATE 01000]
>>>>> (Message 4035) Cannot insert duplicate key row in object
>>>>> 'sys.syscommittab' with unique index 'si_xdes_id'. [SQLSTATE 23000]
>>>>> (Error 2601) Failed to flush the commit table to disk in dbid 7 due
>>>>> to error 2601. Check the errorlog for more information. [SQLSTATE
>>>>> 42000] (Error 3999) The statement has been terminated. [SQLSTATE
>>>>> 01000] (Error 3621). The step failed.
>>>>>
>>>>> I was hoping that the weekend full backups would reset the database
>>>>> and then the log backups would run fine after. NOPE. Still having
>>>>> the same issue. And interestingly, or index rebuild job failed with
>>>>> the same error message for this database.
>>>>>
>>>>> SQL 2008 SP1, Enterprise Edition, active-active-active cluster on
>>>>> Windows 2003 R2 x64 SP2
>>>>>
>>>>> Can someone offer any advice?
>>>>>
>>>>> Thanks,
>>>>> Rubens
>>>>
>>>>
From: Rubens on 1 Dec 2009 00:30
Sorry for the late reply as I haven't had a chance to follow-up on this
until now.

That's a fair statement, and I apologize if I came across poorly in this
public group. It wasn't my intention and I do appreciate your comments.

Thank-you,
Rubens

"Kalen Delaney" <please_reply_on_newsgroups(a)domain.com> wrote in message
news:311BD86E-1FA4-46E2-9C9D-4BE671687EAD(a)microsoft.com...
> My only concern was you stating that you were 'stunned' at Kevin's
> assumptions, as if he/we should know what else you had been doing.
>
> --
> HTH
> Kalen
> ----------------------------------------
> Kalen Delaney
> SQL Server MVP
> www.SQLServerInternals.com
>
> "Rubens" <rubensrose(a)hotmail.com> wrote in message
> news:9965416C-07B8-4EF7-AF6F-3F4FD20723A0(a)microsoft.com...
>> Hi Kalen,
>>
>> As you can imagine, it was a rather urgent situation and yes, I did fail
>> to mention that I had contacted Microsoft first.
>>
>> My original post was a question for a serious problem and the reply I
>> received was not a constructive one. That was what I found surprising.
>>
>> I'd like to ask you this. What "help" did Kevin offer in his post other
>> than to criticize me for posting such a critical issue to this newsgroup?
>> His reply only indicated he was stunned I came here.
>>
>> If anything, the fact that I posted here indicates the respect I have for
>> the level of expertise I've received in the past, and not just from
>> yourself, but other MVP's such as Kevin. I have and still do consider
>> you all a very valuable resource, and I have a lot of respect for your
>> posts.
>>
>> When you have something as critical as what I posted, it's
>> all-hands-on-deck as I am sure you are fully aware. All I was trying to
>> do was make use of all the resources available to me to educate myself on
>> the problem so I could hit the ground running.
>>
>> I obviously did not have the technical expertise to resolve this on my
>> own, which is again why I reached out. And if you read every post I've
>> ever made, you will see just how thankful I have been to the community
>> for their assistance.
>>
>> Thanks,
>> Rubens
>>
>>
>> "Kalen Delaney" <please_reply_on_newsgroups(a)domain.com> wrote in message
>> news:59CC9286-A0BD-4CE1-A185-B65D818AE01D(a)microsoft.com...
>>> Hi Rubens
>>>
>>> Why are you stunned? You never mentioned you were looking elsewhere for
>>> help.
>>>
>>> Are you assuming everybody knew exactly how competent you are just from
>>> the contents of this post? Have you read some of the other posts here to
>>> see what people expect from this forum?
>>>
>>> We get posts that say "EMERGENCY... PLEASE ANSWER IMMEDIATELY... My
>>> production database is marked suspect and nobody can use it. WHAT DO I
>>> DO?"
>>>
>>> Saying that you're stunned implies you expected more from someone, and
>>> that could be construed as criticism. I suggest you try NOT to
>>> criticize the people who are donating their free time and volunteering
>>> to help you on this forum. I understand you might not want to appear
>>> less competent than you think you are, but criticizing Kevin, who has
>>> been providing high quality volunteer help for years, doesn't help your
>>> image.
>>> --
>>> HTH
>>> Kalen
>>> ----------------------------------------
>>> Kalen Delaney
>>> SQL Server MVP
>>> www.SQLServerInternals.com
>>>
>>> "Rubens" <rubensrose(a)hotmail.com> wrote in message
>>> news:C598299C-72D1-4B15-A565-4CDA17ED5189(a)microsoft.com...
>>>> I'm a little stunned that you'd make the assumption that this was all I
>>>> was doing. I already had a call into Microsoft when I posted this and
>>>> was waiting for a call back, so I was looking to this group to provide
>>>> me a little direction as I was researching the problem on my own.
>>>>
>>>> Thanks for your help Kevin.
>>>>
>>>> Rubens
>>>>
>>>> "TheSQLGuru" <kgboles(a)earthlink.net> wrote in message
>>>> news:4ISdnWvcFrOt-JbWnZ2dnUVZ_uednZ2d(a)earthlink.com...
>>>>> Gotta say I am pretty stunned that you have failing backups and a
>>>>> potentially corrupted system on a 1.7TB OLTP system and you are
>>>>> hunting and pecking here on a forum for help? This should be zooming
>>>>> up the food chain at Microsoft customer support...
>>>>>
>>>>> --
>>>>> Kevin G. Boles
>>>>> Indicium Resources, Inc.
>>>>> SQL Server MVP
>>>>> kgboles a earthlink dt net
>>>>>
>>>>>
>>>>> "Rubens" <rubensrose(a)hotmail.com> wrote in message
>>>>> news:0D1604E3-BB25-488E-8251-4BFF84C5A257(a)microsoft.com...
>>>>>>I have a rather concerning issue on our OLTP system for our largest
>>>>>>database (1.7 TB's). On Friday (when I was on vacation of course), we
>>>>>>had a power outage and the cluster failed. Everything was brought
>>>>>>back online from the Network guys, and then our team of DBA's took
>>>>>>over with making sure SQL was ok using the documentation we have.
>>>>>>Since then, the log backups for the above database began to fail, but
>>>>>>it still appears to be writing the log files. We do weekly full
>>>>>>backups, followed by daily differentials. My hope was that after the
>>>>>>full backup ran, everything would be fine with the log backups. Nope,
>>>>>>they are still failing with the error message below...
>>>>>>
>>>>>> Processed 127550 pages for database 'Focus', file 'Focus2000_Log' on
>>>>>> file 1. [SQLSTATE 01000] (Message 4035) Processed 0 pages for
>>>>>> database 'Focus', file 'Focus2000_Log3' on file 1. [SQLSTATE 01000]
>>>>>> (Message 4035) Cannot insert duplicate key row in object
>>>>>> 'sys.syscommittab' with unique index 'si_xdes_id'. [SQLSTATE 23000]
>>>>>> (Error 2601) Failed to flush the commit table to disk in dbid 7 due
>>>>>> to error 2601. Check the errorlog for more information. [SQLSTATE
>>>>>> 42000] (Error 3999) The statement has been terminated. [SQLSTATE
>>>>>> 01000] (Error 3621). The step failed.
>>>>>>
>>>>>> I was hoping that the weekend full backups would reset the database
>>>>>> and then the log backups would run fine after. NOPE. Still having
>>>>>> the same issue. And interestingly, or index rebuild job failed with
>>>>>> the same error message for this database.
>>>>>>
>>>>>> SQL 2008 SP1, Enterprise Edition, active-active-active cluster on
>>>>>> Windows 2003 R2 x64 SP2
>>>>>>
>>>>>> Can someone offer any advice?
>>>>>>
>>>>>> Thanks,
>>>>>> Rubens
>>>>>
>>>>>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Install SQL2008 Std edtn x64
Next: Enable Full Text Search