You just need the following:

FROM        

 dbo.OccMain ocm

 INNER JOIN dbo.OccMalignant omg ON ocm.AilmentID = omg.AilmentID

 LEFT JOIN dbo.CodeLookUp c ON c.Code=omg.SentNode

The security model used in SQL2000 to manage SQL Agent jobs is very limited.

A user who is not a Syadmin can only manage jobs they own.

A user who is a Sysadmin...

I doubt if Microsoft would be interested in giving free consultancy for a 400GB database, as this is well within SQL Server's capabilities.  However, if you are struggling with how to...

If you are using dynamic disks then you are likely to have problems in what you are doing.

Each server has its own Windows (i.e. Access-format) database of information about dynamic...

I echo what has been said about removing autoshrink.  This is a performance killer.  Also make sure autoshrink is off on Tempdb.

You also need to avoid autogrowing your databases if...

Make sure you have security mode set to Windows only.  Mixed mode authentication is inherently less secure.

Using Windows only authentication means no-one can connect using the sa account, even if they...

Unless you use ORDER BY in your query, the last row presented in any display may not be the most recently crated row in the table.

Therefore if you care about the...

This is almost certainly a Windows network authentication problem.

You will need to talk to your Infrastructure people to find out if you have authority to connect to the server from your...

According to MS, if you have SQL2000 Enterprise installed, you can have as many additional instances as you want for no extra license fee.

You need the /PAE switch in your BOOT.INI.  Without this, Windows will ignore everything above the 4GB line.

The MS KB articles are a bit ambiguous about the need for /PAE...

You should benchmark performance before and after making these changes.

If you have your data split into multiple filegroups and files, SQL will start an i-o stream for each file.  In...

My understanding is that extended stored procedures will exist in SQL2005, but will be deprecated.

From SQL2005 onwards you will have .Net CLR support directly within SQL Server.  This means you...

Frank's link has some good stuff.  I would recommend you look at some of these things.

However, if you want to stick with just SQL and DB2, you can also do:

a)...

As a few people have said, in SQL Server it is not possible to restrict what anyone with Sysadmin authority can do.  SQL Server simply does not check if a...

Unless you want to re-code some MS supplied SPs, what you want to do CANNOT be done with SQL2000. 

There are some critical SPs that check if you are either...