stops processing @ the rowcount limit...right?
anyway, here is the stored proc code.
CREATE PROCEDURE storedProc_Kill_91stDay
AS
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
SET ROWCOUNT 30000
delete
from newBackupReports
where timeID
<=
dateDiff(ss,'01/01/1970 00:00:00.000',DATEADD(Day, -91, GetDate()))
go
anyway i can tune this puppy up? or any ideas?
thanks!
tony
On Thu, 05 Aug 2004 15:35:15 +0000, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> This has been a sucky issue. If there are network issues or anything, CF can't tell when accessing the DB and has no graceful way of handling it. We use Oracle, if the TNS listner goes off line for like 5 minutes, the CF server basically chokes and dies. Maybe there is a Java approach to this by by of JDBC? I dunno.
>
> TW, maybe you can have that job chunk up the delete? Have it delete only a few rows at a time to min the impact.
>
> --
>
> ---
> Douglas Knudsen
> http://www.cubicleman.com
> "If you don't like something, change it. If you can't change it, change your attitude. Don't complain." - Maya Angelou
>
> its adv. sql server 2000
> its a sql job.
>
> that aside.
>
> my bigger problem with this...
>
> how does cfmx server/how should cfmx server handle a database that
> just is too busy to feed back a requested recordset? should it crash
> the cmfx server? or not?
>
> this is the bigger problem, i think.
>
> ill fix the db. whats the problem with cfmx?
>
> tw
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
