Can someone tell me what schedule task I need to run. I have a daily
backup, log trimming (exec trimlogs), and start record deletion (Exec
DeleteStartRecords). I also have a weekly database check (Exec
CheckDatabase) that shows up fail, but looks like it works.
-----Original Message-----
From: emerald-request@iea-software.com
[mailto:emerald-request@iea-software.com]On Behalf Of Ronnie Franklin
Sent: Monday, February 14, 2000 4:29 PM
To: emerald@iea-software.com
Subject: RE: [Emerald] Error in stored procedure
Recovery can take minutes to many many hours just according to how many
records, how big the total database and how fast your server is.....
Basically you should NEVER stop your SQL server while you have a long
process going on...
> -----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 6:12 PM
> To: emerald@iea-software.com
> Subject: RE: [Emerald] Error in stored procedure
>
>
> I just tried to stop the stored procedure UpdateCall_serverid but it
> wouldn't respond (it was locking my calls table). So I stopped the SQL
> server process and started it again. Now it is "recovering" my
> sql database.
> What does this mean, how long will this take, what can I do to
> speed it up?
>
> -----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
>
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