I'm a junior developer and going to get my ft wet during my first "real" project. However we're trying to puzzle out a method to set everything as the present developer lives from country.

I had been told to set up certain programs, subversion clients and SQL Server 2000.

It doesn't appear that SQL Server 2000 can be used on Home windows 7. Exist natural difficulties with me developing inside a greater version of SQL Server like 2005? Can there be an problem with saved methods that cannot be correctly converted from on SQL Server version to a different?

Again, I am a newcomer only at that please tell me if this sounds like just an awful idea, impossible and then any other items you can offer.

You will find many features in more recent versions of MSSQL which were not there in 2000 (multi-row card inserts, more recent hashing calculations, and VARCHAR(MAX) to title a couple of). If you are using SQL Server Management Studio, it won't check these variations for you personally, even when you're attached to a SQL server 2000 database - it instantly uses 2008 rules because of its syntax highlighting. Due to this it's not hard to accidentally write code that isn't 2000-compatible.

So far as getting 2000 running, if you possess the install disk to have an older version of home windows, you can operate a VM (http://www.microsoft.com/windows/virtual-pc/) and install the database server there. In case your company includes a separate development atmosphere, you can produce a copy from the production database to operate from too.

The more recent versions of SQL server bring new language and database features, should you write something utilizing a feature that's obtainable in SQL 2005 and never 2000 i.e. PIVOT when you attempt and promote this to reside it will just obtain a syntax error.

There's no translation, should you returned over time 11 years, you'd still speak British you'd just have an odd look should you spoken about 'Tweeting'.

You are able to set the database compatibility level for an earlier version for that specific database you're focusing on. This can prevent you while using more contemporary features.

Typically, you will not encounter issues is you are simply running standard saved methods and SQL claims.

However, you will find a number of things that may not work correctly if you are not synchronized. SQL2005 would be a relatively major upgrade and instroduced a great deal of recent functionality.

I'm not sure what you have for available assets - dollars, etc, but for those who have an MSDN Subscription at an amount that delivers you use of os's, i quickly would highly recommend establishing a virual machine by having an older version of Home windows making use of your MSDN licenses, simply to keep things with an even playing area.