SQL Server Performance Forum – Threads Archive

SQL 2005 Developer version

We are planning to upgrade a SQL 2000 developer version to a SQL 2005 developer version. I can’t find any installation file on-line I can download from. I have two question. 1. There is no download of SQL 2005 developer version (trial or real) available and I will need to purchase it.
2. There is no way for me to upgrade from SQL 2000 developer to SQL 2005 standard without un-installing SQL 2000 developer first. Any clarification on the above is very much appreciated. Wingman

---

1. As far as I know, in SQL Server 2005 editions only SQL Express is free and downloadable. for Developer Edition you have to pay. 2. SQL 2000 and SQL 2005 can co-exists. You can install SQL 2005 in the same machine as a named instance, if SQL 2000 is a default instance. You can take backup of your SQL 2000 database and restore it in SQL 2005 server. Before that, you may run Upgrade Advisor to get a better picture. there are many post in this forum regarding upgradation from 2000 to 2005. Madhu

---

Thanks for the quick response. On #1, what are the major difference between SQL Express and SQL developer?
On #2, actually I was referring to the SQL 2005 developer version, if I already have a SQL 2000 developer default instance installed on a server, can it be co-exist with SQL 2005 developer version installation?
Wingman

---

SQL Server Developer Edition has all the feature of enterprise edition, but licensed only for use as a dvelopment and test system. SQL Express is a free , with little limitation in actual SQL 2005 features available in other versions( it is not having analysis service,notificaton service etc). it is basically a stripped down version of SQL Server 2005 and for low end server users and non-profesional developers. http://www.microsoft.com/sql/editions/developer/default.mspx
Download SQL Express from this site http://msdn.microsoft.com/vstudio/express/sql/download/ 2. Yes , SQL 2005 Developer edition can be a named instance on the same server where your SQL 2000 is a default instance Madhu

---

One of the limitations of 2005 express is: It does not have job scheduler, so you have to utilize some windows utilities if you want to schedule nightly jobs. ——————
Bug explorer/finder/seeker/locator
——————

---

Thanks for the info again. One last question, during the installation of SQL 2005 version, it asks for a service acccount to start services which are SQL server, SQL server agent and SQL browser. As far as I know, SQL browser is new in this list. What type of account is required to start this SQL browser service? Can I use the same account I use to start SQL server for this service? what is the Significance of this SQL browser service?

---

yes, sql server is new in Sql 2005. you can use same service account, there is no problem as such. When you install named instance SQL Server Browser has very important role. To connect to named instance the SQL Server Browser service should be started. It is instance insensitive. http://msdn2.microsoft.com/en-us/library/ms181087.aspx
http://msdn2.microsoft.com/en-us/library/ms165724.aspx
Madhu

---

We have used the same SQL service account used for SQLAgent for SQL Browser too and make sure to check this KBAhttp://support.microsoft.com/kb/914277 for more infomation. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.

---

I have a few more questions. 1. Say we upgraded our SQL 2000 test server to 2005, can our developers who use MS sql analyzer from SQl 2000 still be able to connect to the SQL 2005 server within LAN or via VPN? 2. Will the upgrade affect any stored procedure created in SQL 2000 or any code being developed in MS Access 2000? 3. The test server that we are going to upgrade to SQL 2005, it also does replication to another subscriber computer. If we upgrade the test server(publisher) to SQL 2005 but leave the subscriber server as SQL 2000, is it ok? I have done some testing before and it seems it is ok to have a SQL 2005 server replicates to a SQL 2000 server. Please advise. Wingman

---

1) Refer the following:
http://msdn2.microsoft.com/en-us/library/ms174190.aspx
http://support.microsoft.com/kb/265808

---

]]>