3 Questions on Upgrade to 2k5 2

[AlexCuse]

Hello All,

I have three questions regarding an impending upgrade to SQL Server 2005. This stuff could all pretty easily be answered by a dba, but we don't really have one, so I need your help!

1. How long would be a reasonable time period to get two smallish databases running in production mode for 2005 (from 2000). These are only updated monthly, so I am thinking I will need at least 3 monthly cycles to get everything tested. These are using +/- 10 DTS packages each. Approx 20 stored procs for one and 10 for another. About 20 views each.

2. I know that 2005 SSIS does not support activeX scripting. If I am running existing DTS packages, will existing activeX script tasks (using VBScript) be supported?

3. I have heard that you can run SQL 2000's query analyzer with 2005. What do I need to do to accomplish this?

Any and all insights greatly appreciated,

Thanks,

Alex

A wise man once said
"The only thing normal about database guys is their tables".

 

[mrdenny]

1. The time needed to test everything is directly related to the number of procedures and other sql code which is hitting the database.

2. The legacy DTS packages will continue to run on the SQL 2005 server. You will want to test this ahead of time first.

3. All you need to do is connect with Query Analyzer. I'm not sure why you would want to. The new client tools are much more powerfull once you get the hang of them.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[onpnt]

On the DTS's also do not forget to download the Microsoft SQL Server 2000 DTS Designer Components. You can get them and others here

If you are going to run your upgrade side by side on the same server with 2000 and 2005 make sure you install 2000 first and then 2005 and the add-on. I ran into that problem recently. You'll get entry point errors on the management console if you do the order 2005,DTS Designer and then 2000. Kind of an off the wall issue but in case you hit it.

_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}

 

[AlexCuse]

Thanks for the info, you guys are awesome. Based on what you've provided, I think my estimates are at least reasonable. I will pass along all the advice I've gotten here to the IT department when the time comes for the installation (mid January I believe).

mrdenny - I'll keep working with 2005 at home to try and get the hang of the new Management Studio. I don't necessarily hate it, I guess I am just more comfortable with Query Analyzer. Good to know that moving on might not be such a bad thing.

onpnt - we will be running side by side, so that could be life-saving advice. Thanks for the heads up!

Now comes the fun of convincing my boss I need more time than he thinks to test...

Thanks again,

Alex

A wise man once said
"The only thing normal about database guys is their tables".

 

[Catadmin]

FYI about ActiveX. Microsoft is threatening to stop supporting it in future releases, but has not given a date. Given how vocal they are about it, it could happen in a service pack without warning, or they could be waiting for SQL Server 2008. Who knows.

Anyway, they don't specify if the end of support will include running SQL 2000 DTS packages from the 2k5 DTS components or not, so you'll want to keep an ear open and look towards upgrading the packages at some point anyway.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[onpnt]

Do you think they will go rate to .NET 3.0 then Catadmin?

That actually makes me a bit happy aside from all the work to migrate the ActiveX scripts over. I've always had a thorn in my side when I had to use scripting tech to do some of these things over OO languages. But it did get the job done so you really can't argue unless the performance is an issue witht he coding methods



_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}

 

[Catadmin]

They haven't actually said what they're going to do after they drop ActiveX.

Currently in SSIS, they're encouranging the use of Visual Basic .Net with the 2.0 framework. And you can code some assemblies in C# .Net outside of BIDS to call in your SSIS packages with a VB .Net script task.

The following is the sole opinion of Catadmin and in no way represents the opinion of Tek-Tips, Microsoft or the Scooby Gang: In the process of making things more robust, they're making them more complicated. It seems SQL DBAs now need to know a minimum of 2 programming languages in addition to regular T-SQL. Because in some spots you can use both, in other spots either VB or C# (.Net) only and in some spots (Reporting Services), it seems to be some sort of VBA / VB .Net hash... I don't know what MS is doing.

I'm not sure *they* know what they're doing either, but they are doing something. @=)



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[AlexCuse]

star-fest continues, thanks Cat. I will be starting on rewriting my scripts almost immediately, but because I will need to test new SSIS packages and what not, I hope MS will give a little warning ;-)

Thanks again for all the input guys, it is making me a little more excited about finally getting my hands on this thing. I'm wondering if I should push IT to install evaluation edition earlier? (they are waiting until Jan 11th because of our software assurance plan. If they were to purchase now, we'd have to pay for another whole year in January...)

I've just been told our MS rep is coming in next week, I should be able to find out some more info from him.


A wise man once said
"The only thing normal about database guys is their tables".

 

[onpnt]

I almost feel lucky that I'm leaving the programming field and going into the database end of things with so many years of experience on that side. Makes that added section M$ put in there a bit less of an issue. Although that does seem like an interesting move and something I'm a bit confused on why they would do it. Perhaps it is the revolution of the specialty careers going away and the demand for people that have their skill sets broader over systems than earlier years.


_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}