I believe that PAUSE only prevents new connections being made - any existing connections may still be running. Files are still open, buffers may not have been written to...

What error message(s) are you getting in the logreader agent?

You could be running into a blocking situation. If you have multiple agents running against the distribution database, it is possible...

What Lucky is trying to tell you is check the syntax for isql in BOL, look at the expanded arguments descriptions, and there is one that fixes your issue.

It's just...

Looking more closely at your query *as posted* and the syntax is wrong. DB2 probably will not like the square brackets [], but you definitely need a comma separating your...

It might help if you tell us which version of DB2 you are talking about - and on which platform: Windows/Linux, AS/400 or z/OS mainframe etc.

Also, what was the specific...

Without much detail to go on, the first two things that come to mind are indexes and statistics. Run a profiler trace for 15 minutes or so and save...

Probably obvious and already considered, but if this is for a server array then you need to check how many disks you can physically fit in the server before going...

It's almost certainly an internal user/process.

The profiler trace should tell you where it comes from - but also check the firewall logs.

Could it be some automated process that is trying...

Hi,

BUILTIN\Administrators is a GROUP, so password is controlled for the users at OS level, hence it is NULL in sysxlogins. I guess the two epg\ domain entries are also...

Something like this maybe:

osql -Smyserver -dmaster -E -b -h-1 -r1 -Q "sp_who2" -w200 -n

The -w option sets the page width, which is probably the main cause of data not formatting...

Hi Jenni,

Just be careful deploying MSDE as it is not designed to handle heavy loads and has several limitations.

See the specs here: http://www.microsoft.com/sql/msde/productinfo/features.mspx

and note the Performance area -...

I googled on WAITFOR and found some code example here:

http://groups.google.com/group/comp.databases.ms-sqlserver/browse_thread/thread/3630000094b723fb/a409ce73a64b2cb1%23a409ce73a64b2cb1?sa=X&oi=groupsr&start=0&num=3

Quick example -

DECLARE @DELAYPERIOD NCHAR(12)

SET @DELAYPERIOD = '00:00:01'

DECLARE @Retries INT

SET @Retries = 0

DECLARE @MAXTRIES...

I've seen this happen, I tried to do something similar once before.

There's nothing wrong with your SP. Try running this in Query Analyzer and see what happens:

WHILE 1=1

...

Question - if the dates in both columns have to be the same, what exactly are they used for? Why do you then need both columns? Column B seems...

You can't unfortunately do it in SQL - get your firewall guru to set up appropriate rules to control access to the Prod servers.