Solved

Visual Studio 2003 SQL 2000 issue

Posted on 2013-06-12
7
346 Views
Last Modified: 2013-06-12
We have a small intranet site that functions as a Rolodex which resides in a SQL 2000 database and was created with Visual Studio .NET 2003 Enterprise Edition. We seldom make any updates to it and it has been up and running for years.
We have noticed that end of life support for Visual Studio .NET 2003 Enterprise in October. The question is should we upgrade our Visual Studio .NET 2003 Enterprise version to 2005 and our SQL 2000 database to 2005 just in-case we have any issues?
Is this possible without any conflicts or technical issues and what is the best way to do this? Any assistance offered would be greatly appreciated.
0
Comment
Question by:regsamp
7 Comments
 
LVL 83

Accepted Solution

by:
CodeCruiser earned 167 total points
ID: 39240319
It is possible but will depend on your project.

One thing though, if you are upgrading, why not upgrade to the latest versions or previous to latest versions? Otherwise, you will be panicking and doing this exercise again in couple of years time.
0
 
LVL 10

Assisted Solution

by:Asim Nazir
Asim Nazir earned 166 total points
ID: 39240478
If you have all the code with you then it can be done by simply opening solution to latest/desired visual studio and going through the conversion wizard. Just in case you find any issues, they need to resolved manually.

I am not sure if Microsoft in also ending support for SQLServer or not but if this is the case then you can upgrade to a better version - latest the best.
0
 

Author Comment

by:regsamp
ID: 39240698
So you can open a solution that was created in 2003 with the latest one and there will be a conversion window to do this? And it is fairly easy to go from SQL 2000 to a later issue?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 23

Assisted Solution

by:Racim BOUDJAKDJI
Racim BOUDJAKDJI earned 167 total points
ID: 39240732
upgrading to 2005 does not worth the effort since you will have to buy extended support soon.  I would advise directly moving to 2012.
0
 

Author Comment

by:regsamp
ID: 39240781
Okay Racimo. It looks like SQL 2000 support ended 4/19/13 so will have to upgrade to SQL 2005 or so too.
0
 
LVL 23

Expert Comment

by:Racim BOUDJAKDJI
ID: 39240790
SQL 2005 SP4 support will expire in 2016.
0
 

Author Comment

by:regsamp
ID: 39240792
I saw that. At least that will give us a little while.
0

Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A long time ago (May 2011), I have written an article showing you how to create a DLL using Visual Studio 2005 to be hosted in SQL Server 2005. That was valid at that time and it is still valid if you are still using these versions. You can still re…
Calculating holidays and working days is a function that is often needed yet it is not one found within the Framework. This article presents one approach to building a working-day calculator for use in .NET.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
Viewers will learn how the fundamental information of how to create a table.

895 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now