Sean Pearce (7/11/2013)

ScottPletcher (7/11/2013)

Sean Pearce (7/11/2013)

Pot --> kettle --> black.

Excuse me for being defensive, but Microsoft products have been putting food on...

No problem. That's the most common fix,...

Sean Pearce (7/11/2013)

Pot --> kettle --> black.

Excuse me for being defensive, but Microsoft products have been putting food on my table since...

You could also just add a "GO" after the ALTER TABLE; that will put the SELECTs in a separate batch, by which table SQL should "know" they already exist, having...

After you issue the command(s) below, the next time SQL starts, tempdb will be sized accordingly.

Split the 2GB into equal parts, for however many tempdb data files you have.

For this...

First verify that DTC (Distributed Transaction Coordinator) is up and running properly on both(/all) instances.

I think SQL parses things a batch at a time. All your code is in the same batch, and the table is created in that batch. That might...

It's a kludge, but when I really needed it, I simply change the db context to tempdb if the function already exists in the main db, then delete the function...

ISNULL() has its own oddities:

DECLARE @var1 char(1)

SET @var1 = NULL

SELECT ISNULL(@var1, 'N/A') -- Result = 'N'

I'd suggest using COALESCE also, keeping in mind the difference between it and ISNULL in regard to data types.

Given that, in this case you could explicitly CAST the 99 to...

SELECT

mt.##col1##, ..., jt.##co11##, ...

FROM dbo.maintable mt

LEFT OUTER JOIN jointable jt ON

--ignore last two bytes of patid if they are alpha, because it's...

IIRC, partitioned views are allowed in Standard Edition (at least as long as you don't try to update using a distributed partitioned view?).

As I noted first, a truly partitioned table...

Ouch -- partitioning would be ideal for that situation.

Depending on exact circumstances, you might be able to change the current table to be a view that's defined as a concatenation...

While performance could be adversely affected, possibly severely, the really big problem, at least for a DBA, with data and logs for the same db on the same drive is...

You could implement some type of SNAPSHOT isolation level. That will prevent the types of errors you get with (NOLOCK) and prevent readers from being blocked by writers.

See Books...