-----Original Message-----
From: emerald-request@iea-software.com
[mailto:emerald-request@iea-software.com]On Behalf Of Robert H. Clugston
Sent: Monday, February 14, 2000 3:30 PM
To: emerald@iea-software.com
Subject: RE: [Emerald] Error in stored procedure
I changed the "UpdateCall_accountID" procedure to say 32 instead of 16.
Now when I run the stored procedure "UpdateCall_accountID" I get the
following:
The non_clustered leaf row entry for page 62964 row 0 was not found in index
page 22858 indexid 8 database 'Emerald' (Message 644)
What does this mean?
-----Original Message-----
From: emerald-request@iea-software.com
[mailto:emerald-request@iea-software.com]On Behalf Of Josh Hillman
Sent: Monday, February 14, 2000 2:00 PM
To: emerald@iea-software.com
Subject: Re: [Emerald] Error in stored procedure
From: Robert H. Clugston <robert@csnsys.com>
> Running the stored procedure "UpdateCalls_AccountID" I get the following
> error:
> "Cursorfetch: Maximum length of '@username' is incompatible with that of
> selected column in the cursor (Message 16923)"
>
> Any ideas on how to fix this?
In ISQL, type the following to find out what "length" the Login column is:
sp_help SubAccounts
Then go into the stored procedure and change the following line to reflect
that number:
DECLARE @username varchar(32), @acctid int
In other words if "sp_help subaccounts" returns a length of 16 for Login,
then change the above line to read:
DECLARE @username varchar(16), @acctid int
Or, if you're using SQL 7, you can change the length of the
SubAccounts.Login column to 32...
Josh
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart