Either setup another table with the possible values and create a relationship (good for a lot of items). Or in EM in the design view of the table right click...

Also take your long queries and see if you can write other ways that are more optimized to the SQL 2K environment. It may be a engine differnece causing the...

Have you seen any specific issues?

SQL Server will eat up as much memory as possible based on queries and number of common executions. This is keeping data in memory to...

The point is that sysdatabases in master can be read by any user who connects. Some apps will not show this but if they do

SELECT * FROM master..sysdatabases

it will...

Thanks for the info. I am testing a copy I got and was going to install Windows 2003 and try SQL 2K this weekend.

You leave yuorself vunerable to attacks without an AnitVirus solution.

But if you do install have it set not to scan the MDF, NDF, and LDF files or the backup extension...

Speed for joins either way in most cases are roughly the same due to the way 32bit architecture handles data comparison.

Developers may find either easier but in general it is...

You can either create a job with the TSQL code for doin the backup or setup a maintainence plan to handle this.

I would setup SQL to have a maximum amount allowed so it cannot cram out the OS at all. However, run Profiler to see what major queries happen and you...

With the engine changes you effectively do not know what else is to be qued and thus the data does not have a meaningfull value with regards to troubleshooting. So...

Please do not crosspost. See related topic http://www.sqlservercentral.com/forum/topic.asp?TOPIC_ID=11375&FORUM_ID=9&CAT_ID=1&Topic_Title=Numeric+Primary+Key+vs%2E+Combination+Primary+Key&Forum_Title=General

But the only problem there is you have to own the Server as well. As long as they have an account with Admin access on the Windows OS they can...

I cannot find any details on this one myself even in the sysmessages table. I would have to suggest contacting MS to shead some light on the issue. However, see...

Not really but your concern was the number of joins. But you do get benniffits from having the nullable data in the other table in that you don't waste extra...

Try sliding the dates based on the first starting dates month. This will make each period look like the year of period start.

DECLARE @d1 AS...