Hi Ken

If your table is just needed for any offline information which are not related to the rest of your database you can either keep a local Access database or...

The DBA brought up a good idea. We'll switch the EAV database (which should cause the most load of the server) to another server this night and monitor the error...

Hi Wes

Thanks for the link. The advised hotfix didn't work in our case. The hotfix was contained in SP1 (and SP3 - again) but...

No worries Flo, increases in the -g switch have resolved quite a few memory issues in the past for various clients. I know that you have probably increased this from...

Hi Lynn!

Thanks for your help.

Yes, AWE is enabled for SQL Server.

Yes the server is a physical and...

I think, we can forget the hardware problems (spoke with our DBA). We just had a larger maintenance some weeks ago. Whenever we have a maintenance we switch to the...

Just happened 14th time today...

I noticed (from error-log) that almost all memory caches at zero KB except the MEMORYCLERK_SQLBUFFERPOOL. I'm not sure if this might be the problem.

I attached a...

Hi

I really don't think it makes sense that you just get any statements from here you don't understand. Please have a look to CREATE PROCEDURE. You really should know what...

Hi

We don't use the service broker in our scenario. (Could any other activities implicit cause this?)

Tempdb is stored on an own disk (only shared with the "distribution" database for replication)....

As the error says, you have to use CONVERT to convert an incremental number to a CHAR column.

Take this and move it to a procedure:

DECLARE

@table VARCHAR(100)

,@date VARCHAR(30)

,@sql VARCHAR(1000);

SELECT

@table = 'mytable'

,@date =...

Hi

Some questions:

* Do you pass a parameter of your first table/function to your left-joined function?

* Do you need the sub-query? If yes, did you try to move it into a...

First let me correct your sample SQL

create table #table1 (colA INT, colB INT)

create table #table2 (colA INT)

insert into #table1 values (1, 567)

insert into #table2 values (1)

insert into #table2 values (1)

insert...

Anyway... On SQL Server 2000 the only secure way to do this is a exclusive lock for your table and a index hint over your PK-column:

IF (OBJECT_ID('tempdb..#t') IS NOT NULL)

...

Hi AJ

Thanks for the really useful link. I'll definitely share this with our DBAs!

In this special case (I forgot to say this, sorry...) I already have trace files which have...