# Updating SQL Server 6.5

Yes, I recognize. The presence of a running duplicate of SQL Server 6.5 in 2008 is silly.

That specified, what is the most effective means to move from 6.5 to 2005? Exists any kind of straight course? A lot of the documents I've located manage updating 6.5 to 7.

Should I forget the indigenous SQL Server upgrade energies, manuscript out every one of the things and also information, and also attempt to recreate from square one?

I was mosting likely to try the upgrade this weekend break, yet web server concerns pressed it back till next. So, any kind of suggestions would certainly rate throughout the training course of the week.

Update. This is just how I wound up doing it:

• Back up the database concerned and also Master on 6.5.
• Execute SQL Server 2000's instcat.sql versus 6.5's Master. This permits SQL Server 2000's OLEDB carrier to connect to 6.5.
• Usage SQL Server 2000's standalone "Import and Export Data" to create a DTS plan, making use of OLEDB to connect to 6.5. This efficiently replicated all 6.5's tables to a new 2005 database (additionally making use of OLEDB).
• Usage 6.5's Enterprise Manager to manuscript out every one of the database's indexes and also causes to a.sql documents.
• Execute that.sql documents versus the new duplicate of the database, in 2005's Management Studio.
• Usage 6.5's Enterprise Manager to manuscript out every one of the saved treatments.
• Execute that .sql documents versus the 2005 database. Numerous loads sprocs had concerns making them inappropriate with 2005. Mostly non-ANSI joins and also quoted identifier issues.
• Dealt with every one of those concerns and also re-executed the .sql documents.
• Recreated the 6.5's logins in 2005 and also provided ideal approvals.

There was a little rinse/repeat when dealing with the saved treatments (there were thousands of them to deal with), yet the upgrade went wonderful or else.

Having the ability to make use of Management Studio as opposed to Query Analyzer and also Enterprise Manager 6.5 is such an impressive distinction. A couple of record questions that took 20-30 secs on the 6.5 database are currently running in 1-2 secs, with no alteration, new indexes, or anything. I really did not anticipate that sort of prompt renovation.

0
2019-05-07 00:21:44
Source Share

Hey, I'm still embeded that camp also. The 3rd party application we need to sustain is FINALLY mosting likely to 2K5, so we're virtually out of the timber. Yet I feel your discomfort 8 ^ D

That claimed, from every little thing I learnt through our DBA, the key is to transform the database to 8.0 layout first, and afterwards most likely to 2005. I think they made use of the constructed in migration/upgrade devices for this. There are some large actions in between 6.5 and also 8.0 that are much better addressed there than going from 6.5 to 2005 straight.

Your BIGGEST discomfort, if you really did not recognize currently, is that DTS is entered support of SSIS. There is a shell type component that will certainly run your existing DTS plans, yet you're mosting likely to intend to by hand recreate them done in SSIS. Reduce of this will certainly rely on the intricacy of the plans themselves, yet I've done a couple of at the workplace until now and also they've been rather smooth.

0
2019-05-08 19:51:53
Source

You can update 6.5 to SQL Server 2000. You might have a less complicated time finding SQL Server or the 2000 variation of the MSDE. Microsoft has a web page on going from 6.5 to 2000. As soon as you have the database in 2000 layout, SQL Server 2005 will certainly have no problem updating it to the 2005 layout.

If you do not have SQL Server 2000, you can download the MSDE 2000 variation straight from Microsoft.

0
2019-05-07 17:30:05
Source

I am never reliable, yet I think the only sustained course is from 6.5 to 7. Absolutely that would certainly be one of the most rational course, after that I think you can move from 7 straight to 2005 rather painlessly.

When it comes to scripting out all the things - I would certainly discourage it as you will certainly miss out on something (unless your database is absolutely unimportant ).

0
2019-05-07 16:45:06
Source

If you can locate a specialist or a few other super-enterprise variation of Visual Studio 6.0 - it featured a duplicate of MSDE (Basically the precursor to SQL Express ). I think MSDE 2000 is still readily available as a free download from Microsoft, yet I do not recognize if you can move straight from 6.5 to 2000.

I assume in principle, you will not likely encounter any kind of threat. Years of technique nonetheless inform me that you will certainly constantly miss out on some object, approval, or various other database thing that will not materialize itself quickly. If you can manuscript out the whole dump, the far better. As you will certainly be much less most likely to miss out on something - and also if you do miss out on something, it can be conveniently included in the manuscript and also dealt with. I would certainly stay clear of any kind of hand-operated actions (apart from striking the enter key as soon as ) like the torment.

0
2019-05-07 16:40:51
Source