Friday, March 9, 2012

Error, when alter table

Hi,
on a SQL Server 200 installed on a Win2003 Std. Server, we get an error in a
ny Databse when trying to 'alter table'
The error says something like 'Cursor not vaild' or in German 'Ungueltiger C
ursorstatus'
Any ideas?
Thanks in advanceDid you try running an explicit ALTER TABLE statement in Query Analyzer,
instead of making changes using Enterprise Manager?
http://www.aspfaq.com/2515
http://www.aspfaq.com/
(Reverse address to reply.)
"DOKOM@.community.nospam" <DOKOM@.community.nospam@.discussions.microsoft.com>
wrote in message news:A51F71F0-A5DD-43B9-B849-B3B26759C929@.microsoft.com...
> Hi,
> on a SQL Server 200 installed on a Win2003 Std. Server, we get an error in
any Databse when trying to 'alter table'
> The error says something like 'Cursor not vaild' or in German 'Ungueltiger
Cursorstatus'
> Any ideas?
> Thanks in advance|||Hi again,
your suggestions work fine with the QueryAnalyzer. But beside that, we are f
acing the problem, that some asp-Scripts do not work when performing a 'rs.U
pdate'
They show error: (80040e23) 'Cursor operation conflict'
The Scripts worked fine before.
"Aaron [SQL Server MVP]" wrote:

> Did you try running an explicit ALTER TABLE statement in Query Analyzer,
> instead of making changes using Enterprise Manager?
> http://www.aspfaq.com/2515
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "DOKOM@.community.nospam" <DOKOM@.community.nospam@.discussions.microsoft.com
> wrote in message news:A51F71F0-A5DD-43B9-B849-B3B26759C929@.microsoft.com..
.
> any Databse when trying to 'alter table'
> Cursorstatus'
>
>|||> some asp-Scripts do not work when performing a 'rs.Update'
Call a stored procedure or use an UPDATE statement to perform an update.
Don't use a heavy, lock-intensive recordset object...
http://www.aspfaq.com/2191
http://www.aspfaq.com/
(Reverse address to reply.)|||That might be true, but the Scripts workes on our 'old' Server.
The only thing we want is the scripts running in the 'new' environment.
We will not change everything because of some bad SQL-Patches.
If it is the only chance I'd prefer installing a new instance of the SQL-Ser
ver without the above mentioned Patch.
"Aaron [SQL Server MVP]" wrote:

> Call a stored procedure or use an UPDATE statement to perform an update.
> Don't use a heavy, lock-intensive recordset object...
> http://www.aspfaq.com/2191
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>|||That might be true, but the Scripts workes on our 'old' Server.
The only thing we want is the scripts running in the 'new' environment.
We will not change everything because of some bad SQL-Patches.
If it is the only chance I'd prefer installing a new instance of the SQL-Ser
ver without the above mentioned Patch.
"Aaron [SQL Server MVP]" wrote:

> Call a stored procedure or use an UPDATE statement to perform an update.
> Don't use a heavy, lock-intensive recordset object...
> http://www.aspfaq.com/2191
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>|||> If it is the only chance I'd prefer installing a new instance of the
SQL-Server without the above mentioned Patch.
Did you actually read the whole article I referenced? Here it is again,
just in case:
http://www.aspfaq.com/2515
http://www.aspfaq.com/
(Reverse address to reply.)

No comments:

Post a Comment