"sp_cursor" error while printing web report using Reporting Servic

Hi there,
We're using MS SQL 2000 with MS Server 2003. It's a Xeon ( single processor)
based Server with 1GB RAM.
We also use 'Reporting Services' to generate web reports.
The problem is , our application will have problem writing ( ie. INSERT
INTO) to the transaction database if the web reporting is printing data from
the same transaction table.
Following errors were captured in our application.
_sp_cursor:_The_cursor_identifier_value_provided_(xxxxxxx)_is_not_valid
where xxxxxx cpuld be some kind of hex codes , for example 'abcdf08'
,'abcdf03' etc.
Could the MS SQL Server not able to cope during high traffic?
Pls. help.
Thanks.
CD MooHi
This sounds like you may have blocking/deadlocking which rolls back the
reporting services connection. To monitor this check out
http://support.microsoft.com/kb/271509/EN-US/. If you do not need to report
on the currently live data, then you would be better creating a copy
periodically and point the reports to that. If you need more up-to-date data
you may want to check out log shipping. With SQL 2005 you could use database
snapshots for this purpose.
John
"CD Moo" wrote:
> Hi there,
> We're using MS SQL 2000 with MS Server 2003. It's a Xeon ( single processor)
> based Server with 1GB RAM.
> We also use 'Reporting Services' to generate web reports.
> The problem is , our application will have problem writing ( ie. INSERT
> INTO) to the transaction database if the web reporting is printing data from
> the same transaction table.
> Following errors were captured in our application.
> _sp_cursor:_The_cursor_identifier_value_provided_(xxxxxxx)_is_not_valid
> where xxxxxx cpuld be some kind of hex codes , for example 'abcdf08'
> ,'abcdf03' etc.
> Could the MS SQL Server not able to cope during high traffic?
> Pls. help.
> Thanks.
> CD Moo
>|||Hi there,
We're using SQL Server 2000 with the latest service pack.
I have 2 SQL Servers, Server1 & Server2.
I created a table named Trade in Server1.
Created a view named vwTrade in Server2.
At first, I can see the data from vwTrade. Then I deleted the content of
Trade. Uploaded it with a new set of data using DTS from a foxpro database.
but after that, it is can no longer be seen in vwTrade. If I create another
view named vwTrade2 in Server1, it works fine. But when the view is
recreated in Server2, it just give and empty rowset.
Regards,
Jefrey

"sp_cursor" error while printing web report using Reporting Servic

Hi there,
We're using MS SQL 2000 with MS Server 2003. It's a Xeon ( single processor)
based Server with 1GB RAM.
We also use 'Reporting Services' to generate web reports.
The problem is , our application will have problem writing ( ie. INSERT
INTO) to the transaction database if the web reporting is printing data from
the same transaction table.
Following errors were captured in our application.
_sp_cursor:_The_cursor_identifier_value_
provided_(xxxxxxx)_is_not_valid
where xxxxxx cpuld be some kind of hex codes , for example 'abcdf08'
,'abcdf03' etc.
Could the MS SQL Server not able to cope during high traffic?
Pls. help.
Thanks.
CD MooHi
This sounds like you may have blocking/deadlocking which rolls back the
reporting services connection. To monitor this check out
http://support.microsoft.com/kb/271509/EN-US/. If you do not need to report
on the currently live data, then you would be better creating a copy
periodically and point the reports to that. If you need more up-to-date data
you may want to check out log shipping. With SQL 2005 you could use database
snapshots for this purpose.
John
"CD Moo" wrote:

> Hi there,
> We're using MS SQL 2000 with MS Server 2003. It's a Xeon ( single processo
r)
> based Server with 1GB RAM.
> We also use 'Reporting Services' to generate web reports.
> The problem is , our application will have problem writing ( ie. INSERT
> INTO) to the transaction database if the web reporting is printing data fr
om
> the same transaction table.
> Following errors were captured in our application.
> _sp_cursor:_The_cursor_identifier_value_
provided_(xxxxxxx)_is_not_valid
> where xxxxxx cpuld be some kind of hex codes , for example 'abcdf08'
> ,'abcdf03' etc.
> Could the MS SQL Server not able to cope during high traffic?
> Pls. help.
> Thanks.
> CD Moo
>