If you have no control over the release process, at least you could apply the changes to a test environment before going live. If it breaks the replication in test,...

SQL Server uses as much memory as it can. It's a normal behaviour.

If you have other processes running on the server and you need to allocate memory to them, you...

Confirmed.

UNIQUE and PRIMARY KEY constraints must be enforced by a UNIQUE index.

You're welcome.

Glad I could help

Have you tried using variables instead of parameters?

Another option would be OPTION RECOMPILE on the statement or WITH RECOMPILE on the procedure. I don't remember exactly when it was fixed,...

I'm glad you sorted it out.

However, if it is a 32 bit server, you won't be able to use more than 3 GB of RAM without AWE enabled. Is that...

We would need table scripts, sample data and expected results to give a sensible answer. See the first article linked in my signature line if you're in doubt.

Without any of...

DBCC SHOWCONTIG is your only option in SQL 2000.

This code fragment should help you setting up the procedure:

IF OBJECT_ID('tempdb..#contig') IS NOT NULL DROP TABLE #contig;

CREATE TABLE #contig (

DatabaseName NVARCHAR(128)...

I'm pretty sure you didn't change only xp_cmdshell from 0 to 1, but you (or somebody else before you) changed AWE from 0 to 1.

In order to use AWE, you...

Database Mail cannot process read receipts.

You could put some sort of hack in place, like including an image in the message body, with a link to your website. Most email...

You can create a UNIQUE INDEX on a view.

I don't understand how sequences relate to this topic, though. Can you clarify please?

You can achieve the same thing with subqueries. If you're after better performance, I'm not sure that rewriting the query this way will improve things.

Also, consider that the semantics changed...

Shot in the dark...

Could be a stale statistics issue. If the query runs fine for a couple of days and then start misbehaving, you statistics might be outdated due to...

A bit vague, can you clarify please?

Do you have an example?

Let me suggest a couple of minor changes:

CREATE/ALTER PROCEDURE < PROCEDURE_NAME >

AS

BEGIN

DECLARE @sessid SMALLINT

DECLARE @idle_time_out INT;

DECLARE @sql varchar(20);

...