Do I need to keep SQL Server 2000 for use with my legacy asp site

[gringolalo]

I am an end user more than a technician. My company was originally built around a database system built by a Clipper programmer on DOS. It was then converted to a WEB based site using .ASP, VB and whatever else was the most powerful about five years ago. It works well but things are changing and my .ASP programmer is no longer available.

I am moving the site to a new host and I am upgrading our individual computers to ones using Vista instead of XP. I am having trouble getting a copy of Enterprise Manager for use on my Vista computer. My new host is suggesting upgrading the client server to SQL 2005 so I can use the SQL Server 2005 Management Studio to access my data directly.

Q. Will moving my .ASP code to a SQL 2005 server potentially cause any problems with the flawless way the program functions now?

Q. Is staying with .ASP instead of ASP.NET going to cause me any problems in the next five years because of obsolescence?

Q. Is staying with SQL 2000 going to cause me any problems in the next five years because of obsolescence?

Thank you.

[jhardman]

I am an end user more than a technician. My company was originally built around a database system built by a Clipper programmer on DOS. It was then converted to a WEB based site using .ASP, VB and whatever else was the most powerful about five years ago. It works well but things are changing and my .ASP programmer is no longer available.

I am moving the site to a new host and I am upgrading our individual computers to ones using Vista instead of XP. I am having trouble getting a copy of Enterprise Manager for use on my Vista computer. My new host is suggesting upgrading the client server to SQL 2005 so I can use the SQL Server 2005 Management Studio to access my data directly.

Q. Will moving my .ASP code to a SQL 2005 server potentially cause any problems with the flawless way the program functions now?

it shouldn't (but cross your fingers). One of SQL's big strengths is that the language used to interact with the db is very standardized. although some new features have been added, I don't know of any old methods that won't work with the new.

Q. Is staying with .ASP instead of ASP.NET going to cause me any problems in the next five years because of obsolescence?

not in 5 years, M$ has said that IIS would continue to support "classic" asp in the foreseeable future, but I would recommend that as pages need updating, you update the scripts as well.

Q. Is staying with SQL 2000 going to cause me any problems in the next five years because of obsolescence?

absolutely not, ASP actually interacts with the db through an intermediary that handles specifics. The ODBC drivers that run the db connections might need to be downloaded if you switch machines, but there is no other reason you would have problems.

Thank you.

You're welcome. Let me know if this helps.

Jared