Backing up secondary DB in log shipping ...

Hello can someone clear this up for me?
In BOL "Log Shipping Tips and Best Practices" is the following
recommendation:
"Generating Database Backups from the Secondary
Since the log shipped database is only a small increment of time out
of sync with the primary database, it is a good idea to use it to
generate the full database backups. This would keep the primary
production server free of the potential overhead and contention
incurred by a daily (or scheduled) backup. "
In my experience and from searching other threads in this group this
is actually not true - backing up the log shipped database will not
work, it will fail with the error:
"Database is in warm-standby state (set by executing RESTORE WITH
STANDBY) and cannot be backed up until the entire load sequence is
completed."
Am I missing something or is BOL just being misleading?
thanks,
Peter
Peter,
http://support.microsoft.com/kb/311115 contains the correction.
Note: With SQL Server 2005, you it might be possible to create a snapshot
database over the secondary and back that up. (But I have no experience
with trying.)
RLF
<peter.wismer@.gmail.com> wrote in message
news:1187280994.613717.77730@.l22g2000prc.googlegro ups.com...
> Hello can someone clear this up for me?
> In BOL "Log Shipping Tips and Best Practices" is the following
> recommendation:
> "Generating Database Backups from the Secondary
> Since the log shipped database is only a small increment of time out
> of sync with the primary database, it is a good idea to use it to
> generate the full database backups. This would keep the primary
> production server free of the potential overhead and contention
> incurred by a daily (or scheduled) backup. "
> In my experience and from searching other threads in this group this
> is actually not true - backing up the log shipped database will not
> work, it will fail with the error:
> "Database is in warm-standby state (set by executing RESTORE WITH
> STANDBY) and cannot be backed up until the entire load sequence is
> completed."
> Am I missing something or is BOL just being misleading?
> thanks,
> Peter
>
|||On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Peter,
> http://support.microsoft.com/kb/311115contains the correction.
> Note: With SQL Server 2005, you it might be possible to create a snapshot
> database over the secondary and back that up. (But I have no experience
> with trying.)
> RLF<peter.wis...@.gmail.com> wrote in message
> news:1187280994.613717.77730@.l22g2000prc.googlegro ups.com...
>
>
>
>
>
> - Show quoted text -
Thanks very much Russell (I was beginning to mistrust my command of
the english language - thought I might need to find a Canadian
translation of BOL...)
Peter
|||I think it was a case of wishes versus reality. - RLF
<peter.wismer@.gmail.com> wrote in message
news:1187288061.528821.290710@.j4g2000prf.googlegro ups.com...
> On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Thanks very much Russell (I was beginning to mistrust my command of
> the english language - thought I might need to find a Canadian
> translation of BOL...)
> Peter
>

Backing up secondary DB in log shipping ...

Hello can someone clear this up for me?
In BOL "Log Shipping Tips and Best Practices" is the following
recommendation:
"Generating Database Backups from the Secondary
Since the log shipped database is only a small increment of time out
of sync with the primary database, it is a good idea to use it to
generate the full database backups. This would keep the primary
production server free of the potential overhead and contention
incurred by a daily (or scheduled) backup. "
In my experience and from searching other threads in this group this
is actually not true - backing up the log shipped database will not
work, it will fail with the error:
"Database is in warm-standby state (set by executing RESTORE WITH
STANDBY) and cannot be backed up until the entire load sequence is
completed."
Am I missing something or is BOL just being misleading?
thanks,
PeterPeter,
http://support.microsoft.com/kb/311115 contains the correction.
Note: With SQL Server 2005, you it might be possible to create a snapshot
database over the secondary and back that up. (But I have no experience
with trying.)
RLF
<peter.wismer@.gmail.com> wrote in message
news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
> Hello can someone clear this up for me?
> In BOL "Log Shipping Tips and Best Practices" is the following
> recommendation:
> "Generating Database Backups from the Secondary
> Since the log shipped database is only a small increment of time out
> of sync with the primary database, it is a good idea to use it to
> generate the full database backups. This would keep the primary
> production server free of the potential overhead and contention
> incurred by a daily (or scheduled) backup. "
> In my experience and from searching other threads in this group this
> is actually not true - backing up the log shipped database will not
> work, it will fail with the error:
> "Database is in warm-standby state (set by executing RESTORE WITH
> STANDBY) and cannot be backed up until the entire load sequence is
> completed."
> Am I missing something or is BOL just being misleading?
> thanks,
> Peter
>|||On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Peter,
> http://support.microsoft.com/kb/311115contains the correction.
> Note: With SQL Server 2005, you it might be possible to create a snapshot
> database over the secondary and back that up. (But I have no experience
> with trying.)
> RLF<peter.wis...@.gmail.com> wrote in message
> news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
>
> > Hello can someone clear this up for me?
> > In BOL "Log Shipping Tips and Best Practices" is the following
> > recommendation:
> > "Generating Database Backups from the Secondary
> > Since the log shipped database is only a small increment of time out
> > of sync with the primary database, it is a good idea to use it to
> > generate the full database backups. This would keep the primary
> > production server free of the potential overhead and contention
> > incurred by a daily (or scheduled) backup. "
> > In my experience and from searching other threads in this group this
> > is actually not true - backing up the log shipped database will not
> > work, it will fail with the error:
> > "Database is in warm-standby state (set by executing RESTORE WITH
> > STANDBY) and cannot be backed up until the entire load sequence is
> > completed."
> > Am I missing something or is BOL just being misleading?
> > thanks,
> > Peter- Hide quoted text -
> - Show quoted text -
Thanks very much Russell (I was beginning to mistrust my command of
the english language - thought I might need to find a Canadian
translation of BOL...)
Peter|||I think it was a case of wishes versus reality. - RLF
<peter.wismer@.gmail.com> wrote in message
news:1187288061.528821.290710@.j4g2000prf.googlegroups.com...
> On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> Peter,
>> http://support.microsoft.com/kb/311115contains the correction.
>> Note: With SQL Server 2005, you it might be possible to create a snapshot
>> database over the secondary and back that up. (But I have no experience
>> with trying.)
>> RLF<peter.wis...@.gmail.com> wrote in message
>> news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
>>
>> > Hello can someone clear this up for me?
>> > In BOL "Log Shipping Tips and Best Practices" is the following
>> > recommendation:
>> > "Generating Database Backups from the Secondary
>> > Since the log shipped database is only a small increment of time out
>> > of sync with the primary database, it is a good idea to use it to
>> > generate the full database backups. This would keep the primary
>> > production server free of the potential overhead and contention
>> > incurred by a daily (or scheduled) backup. "
>> > In my experience and from searching other threads in this group this
>> > is actually not true - backing up the log shipped database will not
>> > work, it will fail with the error:
>> > "Database is in warm-standby state (set by executing RESTORE WITH
>> > STANDBY) and cannot be backed up until the entire load sequence is
>> > completed."
>> > Am I missing something or is BOL just being misleading?
>> > thanks,
>> > Peter- Hide quoted text -
>> - Show quoted text -
> Thanks very much Russell (I was beginning to mistrust my command of
> the english language - thought I might need to find a Canadian
> translation of BOL...)
> Peter
>

Backing up secondary DB in log shipping ...

Hello can someone clear this up for me?
In BOL "Log Shipping Tips and Best Practices" is the following
recommendation:
"Generating Database Backups from the Secondary
Since the log shipped database is only a small increment of time out
of sync with the primary database, it is a good idea to use it to
generate the full database backups. This would keep the primary
production server free of the potential overhead and contention
incurred by a daily (or scheduled) backup. "
In my experience and from searching other threads in this group this
is actually not true - backing up the log shipped database will not
work, it will fail with the error:
"Database is in warm-standby state (set by executing RESTORE WITH
STANDBY) and cannot be backed up until the entire load sequence is
completed."
Am I missing something or is BOL just being misleading?
thanks,
PeterPeter,
http://support.microsoft.com/kb/311115 contains the correction.
Note: With SQL Server 2005, you it might be possible to create a snapshot
database over the secondary and back that up. (But I have no experience
with trying.)
RLF
<peter.wismer@.gmail.com> wrote in message
news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
> Hello can someone clear this up for me?
> In BOL "Log Shipping Tips and Best Practices" is the following
> recommendation:
> "Generating Database Backups from the Secondary
> Since the log shipped database is only a small increment of time out
> of sync with the primary database, it is a good idea to use it to
> generate the full database backups. This would keep the primary
> production server free of the potential overhead and contention
> incurred by a daily (or scheduled) backup. "
> In my experience and from searching other threads in this group this
> is actually not true - backing up the log shipped database will not
> work, it will fail with the error:
> "Database is in warm-standby state (set by executing RESTORE WITH
> STANDBY) and cannot be backed up until the entire load sequence is
> completed."
> Am I missing something or is BOL just being misleading?
> thanks,
> Peter
>|||On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Peter,
> http://support.microsoft.com/kb/311115contains the correction.
> Note: With SQL Server 2005, you it might be possible to create a snapshot
> database over the secondary and back that up. (But I have no experience
> with trying.)
> RLF<peter.wis...@.gmail.com> wrote in message
> news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
>
>
>
>
>
>
>
>
> - Show quoted text -
Thanks very much Russell (I was beginning to mistrust my command of
the english language - thought I might need to find a Canadian
translation of BOL...)
Peter|||I think it was a case of wishes versus reality. - RLF
<peter.wismer@.gmail.com> wrote in message
news:1187288061.528821.290710@.j4g2000prf.googlegroups.com...
> On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Thanks very much Russell (I was beginning to mistrust my command of
> the english language - thought I might need to find a Canadian
> translation of BOL...)
> Peter
>

Back button does not regenerate original report

When I drill down from one report to another and then depress the back button to return to the initial report, the message 'Generating Report" spins forever without actually running. However, if I depress the regenerate button during this time, it will run the report.

I believe that I may have inadvertingly reset a field attribute to have caused this condition. Ironocally, I have the same set of database installed on another server, and the this does not happen.

I forgot to mention that I am using Report Manager to deploy the reports.

Please assist.

Just checking if anyone has any additional info on this. I'm having the same problem. SQL Server 2005 (SP2), Reporting Services 2005 (SP2).

Any help is appreciated as this is a major usability issue.

|||I am also experiencing this issue.|||I think microsoft fixed this. In vista64/sql64 there is no back button......that I can find.|||This thread is talking about the browser (internet explorer) back button.|||

Can someone from Microsoft please chime in on this issue. If you hit the browser back button from IE from a drilled/jump to report, the original report is not shown. The "Report is being generated" screen just sits there. This is a huge usability issue.

Also, can someone from Microsoft point me to where we're supposed to find out when/if an upcoming SP/hotfix is going to come out and what is included. I want to move our reporting system to Reporting Services but the above issue is one of the reasons I can't.

|||

I am also getting this on multiple machines and databases. I can recreate it starting with 2 simple reports, the main report and a drill down report. The browser back button tries to bring up the original report, but never finishes. I noticed there is always an HTML error on the report that goes away if you click refresh. (Note: The error only shows up if your browser is set to show errors). I am using SQL Service Pack 2 and IE7. The error I get is:

Line: 718

Char: 5

Error: 'location' is null or not an object

Code: 0

URL: ......

|||

I am having this problem too, since we moved to SQL 2005 64-bit,sp2.

With certain reports that are hyperlinked to other reports, pressing the IE back button (to return to the previous report) goes into the endless 'Report is being generated, green spin'. Only by clicking on the report's toolbar refresh button does the report re-display.

This appears to be a problem only with the combination of SQL 2005 64-bit and IE 7. Everything works great! with SQL 2005 32-bit and IE 6 or 7 and even using SQL 2005 64-bit with IE 6. The problem seems to be in IE 7 when SQL 2005 64-bit is the backend database. Any help or advice would be greatly appreciated!

Sam

|||

Are all of you using the 64-bit version? I am using the 32 bit version with IE 7 and have never experienced that problem.

I experience a problem with report viewer where I drilldown into a report and click the next page button. Then mysteriously the parent report displays. It's odd, but not too big of a deal to me.

|||We are on the 64-bit version.

Back button does not regenerate original report

When I drill down from one report to another and then depress the back button to return to the initial report, the message 'Generating Report" spins forever without actually running. However, if I depress the regenerate button during this time, it will run the report.

I believe that I may have inadvertingly reset a field attribute to have caused this condition. Ironocally, I have the same set of database installed on another server, and the this does not happen.

I forgot to mention that I am using Report Manager to deploy the reports.

Please assist.

moving to SQL Server Reporting Services forum.

Back button does not regenerate original report

When I drill down from one report to another and then depress the back button to return to the initial report, the message 'Generating Report" spins forever without actually running. However, if I depress the regenerate button during this time, it will run the report.

I believe that I may have inadvertingly reset a field attribute to have caused this condition. Ironocally, I have the same set of database installed on another server, and the this does not happen.

I forgot to mention that I am using Report Manager to deploy the reports.

Please assist.

Just checking if anyone has any additional info on this. I'm having the same problem. SQL Server 2005 (SP2), Reporting Services 2005 (SP2).

Any help is appreciated as this is a major usability issue.

|||I am also experiencing this issue.|||I think microsoft fixed this. In vista64/sql64 there is no back button......that I can find.|||This thread is talking about the browser (internet explorer) back button.|||

Can someone from Microsoft please chime in on this issue. If you hit the browser back button from IE from a drilled/jump to report, the original report is not shown. The "Report is being generated" screen just sits there. This is a huge usability issue.

Also, can someone from Microsoft point me to where we're supposed to find out when/if an upcoming SP/hotfix is going to come out and what is included. I want to move our reporting system to Reporting Services but the above issue is one of the reasons I can't.

|||

I am also getting this on multiple machines and databases. I can recreate it starting with 2 simple reports, the main report and a drill down report. The browser back button tries to bring up the original report, but never finishes. I noticed there is always an HTML error on the report that goes away if you click refresh. (Note: The error only shows up if your browser is set to show errors). I am using SQL Service Pack 2 and IE7. The error I get is:

Line: 718

Char: 5

Error: 'location' is null or not an object

Code: 0

URL: ......

|||

I am having this problem too, since we moved to SQL 2005 64-bit,sp2.

With certain reports that are hyperlinked to other reports, pressing the IE back button (to return to the previous report) goes into the endless 'Report is being generated, green spin'. Only by clicking on the report's toolbar refresh button does the report re-display.

This appears to be a problem only with the combination of SQL 2005 64-bit and IE 7. Everything works great! with SQL 2005 32-bit and IE 6 or 7 and even using SQL 2005 64-bit with IE 6. The problem seems to be in IE 7 when SQL 2005 64-bit is the backend database. Any help or advice would be greatly appreciated!

Sam

|||

Are all of you using the 64-bit version? I am using the 32 bit version with IE 7 and have never experienced that problem.

I experience a problem with report viewer where I drilldown into a report and click the next page button. Then mysteriously the parent report displays. It's odd, but not too big of a deal to me.

|||We are on the 64-bit version.

Back button does not regenerate original report

When I drill down from one report to another and then depress the back button to return to the initial report, the message 'Generating Report" spins forever without actually running. However, if I depress the regenerate button during this time, it will run the report.

I believe that I may have inadvertingly reset a field attribute to have caused this condition. Ironocally, I have the same set of database installed on another server, and the this does not happen.

I forgot to mention that I am using Report Manager to deploy the reports.

Please assist.

Just checking if anyone has any additional info on this. I'm having the same problem. SQL Server 2005 (SP2), Reporting Services 2005 (SP2).

Any help is appreciated as this is a major usability issue.

|||I am also experiencing this issue.|||I think microsoft fixed this. In vista64/sql64 there is no back button......that I can find.|||This thread is talking about the browser (internet explorer) back button.|||

Can someone from Microsoft please chime in on this issue. If you hit the browser back button from IE from a drilled/jump to report, the original report is not shown. The "Report is being generated" screen just sits there. This is a huge usability issue.

Also, can someone from Microsoft point me to where we're supposed to find out when/if an upcoming SP/hotfix is going to come out and what is included. I want to move our reporting system to Reporting Services but the above issue is one of the reasons I can't.

|||

I am also getting this on multiple machines and databases. I can recreate it starting with 2 simple reports, the main report and a drill down report. The browser back button tries to bring up the original report, but never finishes. I noticed there is always an HTML error on the report that goes away if you click refresh. (Note: The error only shows up if your browser is set to show errors). I am using SQL Service Pack 2 and IE7. The error I get is:

Line: 718

Char: 5

Error: 'location' is null or not an object

Code: 0

URL: ......

|||

I am having this problem too, since we moved to SQL 2005 64-bit,sp2.

With certain reports that are hyperlinked to other reports, pressing the IE back button (to return to the previous report) goes into the endless 'Report is being generated, green spin'. Only by clicking on the report's toolbar refresh button does the report re-display.

This appears to be a problem only with the combination of SQL 2005 64-bit and IE 7. Everything works great! with SQL 2005 32-bit and IE 6 or 7 and even using SQL 2005 64-bit with IE 6. The problem seems to be in IE 7 when SQL 2005 64-bit is the backend database. Any help or advice would be greatly appreciated!

Sam

|||

Are all of you using the 64-bit version? I am using the 32 bit version with IE 7 and have never experienced that problem.

I experience a problem with report viewer where I drilldown into a report and click the next page button. Then mysteriously the parent report displays. It's odd, but not too big of a deal to me.

|||We are on the 64-bit version.

Back button does not regenerate original report

When I drill down from one report to another and then depress the back button to return to the initial report, the message 'Generating Report" spins forever without actually running. However, if I depress the regenerate button during this time, it will run the report.

I believe that I may have inadvertingly reset a field attribute to have caused this condition. Ironocally, I have the same set of database installed on another server, and the this does not happen.

I forgot to mention that I am using Report Manager to deploy the reports.

Please assist.

Just checking if anyone has any additional info on this. I'm having the same problem. SQL Server 2005 (SP2), Reporting Services 2005 (SP2).

Any help is appreciated as this is a major usability issue.

|||I am also experiencing this issue.|||I think microsoft fixed this. In vista64/sql64 there is no back button......that I can find.|||This thread is talking about the browser (internet explorer) back button.|||

Can someone from Microsoft please chime in on this issue. If you hit the browser back button from IE from a drilled/jump to report, the original report is not shown. The "Report is being generated" screen just sits there. This is a huge usability issue.

Also, can someone from Microsoft point me to where we're supposed to find out when/if an upcoming SP/hotfix is going to come out and what is included. I want to move our reporting system to Reporting Services but the above issue is one of the reasons I can't.

|||

I am also getting this on multiple machines and databases. I can recreate it starting with 2 simple reports, the main report and a drill down report. The browser back button tries to bring up the original report, but never finishes. I noticed there is always an HTML error on the report that goes away if you click refresh. (Note: The error only shows up if your browser is set to show errors). I am using SQL Service Pack 2 and IE7. The error I get is:

Line: 718

Char: 5

Error: 'location' is null or not an object

Code: 0

URL: ......

|||

I am having this problem too, since we moved to SQL 2005 64-bit,sp2.

With certain reports that are hyperlinked to other reports, pressing the IE back button (to return to the previous report) goes into the endless 'Report is being generated, green spin'. Only by clicking on the report's toolbar refresh button does the report re-display.

This appears to be a problem only with the combination of SQL 2005 64-bit and IE 7. Everything works great! with SQL 2005 32-bit and IE 6 or 7 and even using SQL 2005 64-bit with IE 6. The problem seems to be in IE 7 when SQL 2005 64-bit is the backend database. Any help or advice would be greatly appreciated!

Sam

|||

Are all of you using the 64-bit version? I am using the 32 bit version with IE 7 and have never experienced that problem.

I experience a problem with report viewer where I drilldown into a report and click the next page button. Then mysteriously the parent report displays. It's odd, but not too big of a deal to me.

|||We are on the 64-bit version.

Back button does not regenerate original report

When I drill down from one report to another and then depress the back button to return to the initial report, the message 'Generating Report" spins forever without actually running. However, if I depress the regenerate button during this time, it will run the report.

I believe that I may have inadvertingly reset a field attribute to have caused this condition. Ironocally, I have the same set of database installed on another server, and the this does not happen.

I forgot to mention that I am using Report Manager to deploy the reports.

Please assist.

Just checking if anyone has any additional info on this. I'm having the same problem. SQL Server 2005 (SP2), Reporting Services 2005 (SP2).

Any help is appreciated as this is a major usability issue.

|||I am also experiencing this issue.|||I think microsoft fixed this. In vista64/sql64 there is no back button......that I can find.|||This thread is talking about the browser (internet explorer) back button.|||

Can someone from Microsoft please chime in on this issue. If you hit the browser back button from IE from a drilled/jump to report, the original report is not shown. The "Report is being generated" screen just sits there. This is a huge usability issue.

Also, can someone from Microsoft point me to where we're supposed to find out when/if an upcoming SP/hotfix is going to come out and what is included. I want to move our reporting system to Reporting Services but the above issue is one of the reasons I can't.

|||

I am also getting this on multiple machines and databases. I can recreate it starting with 2 simple reports, the main report and a drill down report. The browser back button tries to bring up the original report, but never finishes. I noticed there is always an HTML error on the report that goes away if you click refresh. (Note: The error only shows up if your browser is set to show errors). I am using SQL Service Pack 2 and IE7. The error I get is:

Line: 718

Char: 5

Error: 'location' is null or not an object

Code: 0

URL: ......

|||

I am having this problem too, since we moved to SQL 2005 64-bit,sp2.

With certain reports that are hyperlinked to other reports, pressing the IE back button (to return to the previous report) goes into the endless 'Report is being generated, green spin'. Only by clicking on the report's toolbar refresh button does the report re-display.

This appears to be a problem only with the combination of SQL 2005 64-bit and IE 7. Everything works great! with SQL 2005 32-bit and IE 6 or 7 and even using SQL 2005 64-bit with IE 6. The problem seems to be in IE 7 when SQL 2005 64-bit is the backend database. Any help or advice would be greatly appreciated!

Sam

|||

Are all of you using the 64-bit version? I am using the 32 bit version with IE 7 and have never experienced that problem.

I experience a problem with report viewer where I drilldown into a report and click the next page button. Then mysteriously the parent report displays. It's odd, but not too big of a deal to me.

|||We are on the 64-bit version.

avoiding "NaN" , "infinity" in reports

When I use calculation in generating reports, I get "NaN" and "Infinity" values, I wanted to avoid this and display "0" if the result of calculation is null or infinity..

I used the below calculation

=(Fields!approved_tier_cnt.Value)/(Fields!approved_cnt.Value)

Please let me know how to avoid "NaN" and "infinity", while displaying in reports

Regards

Durai

Hello

What I do is tackle those Nan's before they get into RS. On your SQL Server you could make a function something like this:

CREATE FUNCTION formula (
@.Numerator REAL,
@.Denominator REAL,
@.decimals INT = 2,
@.length INT = 10
)
RETURNS VARCHAR(50)
AS BEGIN IF (
@.Denominator IS NULL )
OR (@.Numerator IS NULL )
RETURN '' IF
(@.Denominator <> 0) BEGIN
RETURN str((@.Numerator ) / @.Denominator,@.length - 1, @.decimals)
END
RETURN ''
END

et voila...
put the results in a view

Worf

|||

I would use some explicit type casting and conditional logic.

Firstly to avoid NaN I would make sure the fields are numeric by using one of the standard VB conversion functions e.g. CInt(), CDbl() etc. like this:

=CDbl(Fields!approved_tier_cnt.Value)/CDbl(Fields!approved_cnt.Value)

Then use the Iif() function to check for nulls or check that the divisor is not 0 to avoid infinity

=Iif( Fields!approved_tier_cnt.Value AND
Fields!approved_cnt.Value AND
CDbl(Fields!approved_cnt.Value) != 0
, CDbl(Fields!approved_tier_cnt.Value) / CDbl(Fields!approved_cnt.Value)
, 0
)

AV & contineus stack dumps on SQL7.

Hi,
I've got SQL7-SP3 installation on NT4-SP6. Now, today I
noticed that for number of days it is generating stack
dumps every few minutes. It goes like this:
===================== SqlDumpExceptionHandler: Process 51 generated fatal
exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
is terminating this process.
* BEGIN STACK DUMP:
-
-
-
-
language_exec: Process 51 generated an access violation.
SQL Server is terminating this process.
====================== Input buffer always say:
* select rsc_type, req_mode, req_status from
master..syslockinfo
I tried to search the knowledge base, but it reports tons
of reasons for AV. I have seen AV & stack dumps number of
times in past (on different servers) that goes only for
once, but the one I am looking at currently is doing it
constantly at few minutes interval.
I havn't heard any performance cry yet and don't know how
it is affecting.
Anyone seen this kind of behaviour or have any input on
this are welcome to shed some light. Your input is
appreciated. Thanks.
Adi.We found a monitoring software that was querying
syslockinfo, causing AV and stack dump. Stopping this
monitoring software service stopped stack dumps.
Still I wonder how did it started happening as we have
ditto configuration and setup on number of other servers
where everything seems to be working fine.
Anyways, thanks for your replies guys. Appreciate it.
Adi ..
>--Original Message--
>Hi,
>I've got SQL7-SP3 installation on NT4-SP6. Now, today I
>noticed that for number of days it is generating stack
>dumps every few minutes. It goes like this:
>=====================>SqlDumpExceptionHandler: Process 51 generated fatal
>exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
>is terminating this process.
>* BEGIN STACK DUMP:
>-
>-
>-
>-
>language_exec: Process 51 generated an access violation.
>SQL Server is terminating this process.
>======================>Input buffer always say:
>* select rsc_type, req_mode, req_status from
>master..syslockinfo
>I tried to search the knowledge base, but it reports tons
>of reasons for AV. I have seen AV & stack dumps number of
>times in past (on different servers) that goes only for
>once, but the one I am looking at currently is doing it
>constantly at few minutes interval.
>I havn't heard any performance cry yet and don't know how
>it is affecting.
>Anyone seen this kind of behaviour or have any input on
>this are welcome to shed some light. Your input is
>appreciated. Thanks.
>Adi.
>.
>