Expanding timeout setting for a SQL 2000 database

I have a database with a lot of old records i want to delete.
when i try to make the delete, i get the timeout message.
I don't care that the delete job will run several hours, but for that i need
to configure a large timeout time for a specific database?
Somebody can advice me how to do that?
Thanks in advance,
BarakBarak
Try keep you transactions small, also you will not lock others during the
transaction.
SET ROWCOUNT 1000
WHILE 1 = 1
BEGIN
--Your DELETE statement
IF @.@.ROWCOUNT = 0
BEGIN
BREAK
END
ELSE
BEGIN
CHECKPOINT
END
END
SET ROWCOUNT 0
"Barak Turovsky" <baraktur@.mail.ru> wrote in message
news:#gDxj1t$DHA.2216@.TK2MSFTNGP10.phx.gbl...
> I have a database with a lot of old records i want to delete.
> when i try to make the delete, i get the timeout message.
> I don't care that the delete job will run several hours, but for that i
need
> to configure a large timeout time for a specific database?
> Somebody can advice me how to do that?
> Thanks in advance,
> Barak
>|||Barak Turovsky (baraktur@.mail.ru) writes:
> I have a database with a lot of old records i want to delete. when i try
> to make the delete, i get the timeout message. I don't care that the
> delete job will run several hours, but for that i need to configure a
> large timeout time for a specific database?
The timeout is a client-side thing, so this is nothing you set in your
database.
From where are you running your command? Many client libraries has a default
timeout of 30 seconds. Enterprise Manager has as well. Query Analyzer on
the other hand has no timeout by default.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Expanding timeout setting for a SQL 2000 database

I have a database with a lot of old records i want to delete.
when i try to make the delete, i get the timeout message.
I don't care that the delete job will run several hours, but for that i need
to configure a large timeout time for a specific database?
Somebody can advice me how to do that?
Thanks in advance,
BarakBarak
Try keep you transactions small, also you will not lock others during the
transaction.
SET ROWCOUNT 1000
WHILE 1 = 1
BEGIN
--Your DELETE statement
IF @.@.ROWCOUNT = 0
BEGIN
BREAK
END
ELSE
BEGIN
CHECKPOINT
END
END
SET ROWCOUNT 0
"Barak Turovsky" <baraktur@.mail.ru> wrote in message
news:#gDxj1t$DHA.2216@.TK2MSFTNGP10.phx.gbl...
> I have a database with a lot of old records i want to delete.
> when i try to make the delete, i get the timeout message.
> I don't care that the delete job will run several hours, but for that i
need
> to configure a large timeout time for a specific database?
> Somebody can advice me how to do that?
> Thanks in advance,
> Barak
>|||Barak Turovsky (baraktur@.mail.ru) writes:
> I have a database with a lot of old records i want to delete. when i try
> to make the delete, i get the timeout message. I don't care that the
> delete job will run several hours, but for that i need to configure a
> large timeout time for a specific database?
The timeout is a client-side thing, so this is nothing you set in your
database.
From where are you running your command? Many client libraries has a default
timeout of 30 seconds. Enterprise Manager has as well. Query Analyzer on
the other hand has no timeout by default.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

Execution 'xxxxxx' not found

I am having an issue where I can't get any reports to run no matter how
simple (eliminating the possibility of it being a session timeout problem).
I constantly get an execution not found error as soon as the report starts to
run. It seems to make no difference where I run any report from or if it is
in Sharepoint integrated mode or not.On Sep 10, 1:34 pm, MP <M...@.discussions.microsoft.com> wrote:
> I am having an issue where I can't get any reports to run no matter how
> simple (eliminating the possibility of it being a session timeout problem).
> I constantly get an execution not found error as soon as the report starts to
> run. It seems to make no difference where I run any report from or if it is
> in Sharepoint integrated mode or not.
This link might be helpful.
http://blogs.msdn.com/sharepoint/archive/2007/08/02/microsoft-sql-server-reporting-services-installation-and-configuration-guide-for-sharepoint-integration-mode.aspx
Regards,
Enrique Martinez
Sr. Software Consultant|||Tried everything I could think of and I couldn't track this down. In the end
I think it has something to do with the fact that the WebUsersGroup name is
too long and it replaced it with a id.
The weird thing is when I use a webpart and view the reports that way they
work.
"MP" wrote:
> I am having an issue where I can't get any reports to run no matter how
> simple (eliminating the possibility of it being a session timeout problem).
> I constantly get an execution not found error as soon as the report starts to
> run. It seems to make no difference where I run any report from or if it is
> in Sharepoint integrated mode or not.
>