Wasn't 100% sure which columns went with which tables but try this

Declare @JOnum as char(10)

Set @JOnum = 'I2B98-0000'

SELECT

 jodbom.fjobno

 ,jodbom.fbompart

 ,jodbom.fbomrev

 ,jodbom.fbomdesc

 ,jodbom.fparent

 ,jodbom.fparentrev

 ,jodbom.factqty

 ,jodbom.fbommeas

 ,jodbom.fqty_iss

 ,qalotc.fclot

 ,rcitem.fccompany

FROM

 dbo.jodbom jodbom

LEFT JOIN

 dbo.qalotc qalotc

  JOIN

 dbo.rcitem rcitem

 ON

  rcitem.fReceiver + rcitem.fItemNo = qalotc.fcdoc AND

  rcitem.fctype...

Yes I have to do this often to free the virtual logs in SQL 2000 myself before a shrink will occurr.

If there are ongoing transactions into the transaction log it may not issue a checkpoint (does not truncate however even then) so the log will be marked for use. So...

I would set up a test scenario on another server and make sure you get the condition you want to have happen first. (QA the code)

I always heard it was women you put on the job.

Also I think Steve's comment which I will try to check is that adding people is not always the answer.

Besides...

Have that book myself and it is really good. It depends on the project and the needs to be met. Sometime you have to readjust your schedules because you will...

I know of no hard in stone from MS doc like you want. As for aliasing thou I as well never alias a column name unless there are collisions like...

Looks fine to me and I tested a similar setup with no issues. What is happening that is not as you expect?

RSS is "Reporting Services Script" file which is similar to JScript where RDL is "Report Definition Language". I use it to deploy RDL files all the time. However you have to...

In applications that have to be fully portable between multiple database backends or talk to multiple types of backends at the same time, better off staying in the apps code...

Sounds like maybe it isn't null but maybe blank. Try changing both lines to this

WHEN NullIf(@ReferenceRange,'') IS NULL THEN NULL

I thought officially Jet is dumpped just not all support on it yet has been dumpped. No more MDAC updates at all since 2.8a 2 years ago (as I recall).

Not to my knowledge (at least not directly from T-SQL). You may find a good way using SQL-DMO or SQL-SMO to do this but I don't have an example to provide...

First off you are probably getting due to the fact tblMain.colNumber is a numeric or integer data type where you comparison value is a character type thus a type mismatch...

SQL will not give up memory as it is using for the buffers and caches. This is not an issue but can cause some contention becuase of the fact it...