SQL 2005 Info

[mrdenny]

For those of you who haven't been able to get your hands on a copy of SQL 2005 Beta or CTP here is some good info I've found on Microsoft's site.


SQL 2005 overview for the DBA

http://www.microsoft.com/technet/prodtechnol/sql/2005/maintain/sqlydba.mspx

Top 30 features of SQL 2005

http://www.microsoft.com/sql/2005/productinfo/top30features.mspx

SQL 2005 Product overview

http://www.microsoft.com/sql/2005/productinfo/overview_5.mspx

SQL 2005 Editions Side by Side

http://www.microsoft.com/sql/2005/productinfo/sql2005features.mspx

If anyone has specific questions about the system post them here or in a new thread and I'll reply to what I can. I've got the most recent CTP release and will gladly answer what I can.

Denny
MCSA (2003) / MCDBA (SQL 2000)

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

http://www.mrdenny.com

(My very old site)

 

[vongrunt]

2-node failover clustering and log shipping on SE, snapshot isolation, data partitioning... cool.

Any official link about T-SQL enhancements? Tnx.

------
"There's a man... He's bald and wears a short-sleeved shirt, and somehow he's very important to me. I think his name is Homer."
(Jack O'Neill, Stargate)

 

[mrdenny]

I haven't seen a link for T/SQL enhancements yet.

Denny
MCSA (2003) / MCDBA (SQL 2000)

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

http://www.mrdenny.com

(My very old site)

 

[krios]

I just installed SQL Server 2005 Developer Edition(June CTP) and also currently have sql server 2000 running. it said in the readme file that they could run concurrently without a problem. During the installation, however, it would not let me install a default instance and had to create a named instance. So now, i have 2 instances of a local server (one is named, the other is not - WSKR and WSKR\YUKON). SQL Server now automatically defaults to WSKR\YUKON and can no longer connect to my default instance. I get the following error:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server)

If you can offer any help or suggestions, I'd really appreciate it!!!

Thanks,
Karina

 

[mrdenny]

The reason that you couldn't install it as the default instance, is because you already had a default instance installed. You can only have one default instance on a SQL Server.

Can you telnet to the port that the SQL Server 2000 instance is listening on (usually port 1433)? What if you shutdown the SQL 2005 instance and restart the SQL 2000 instance. Can you connect now? Make sure that the SQL 2005 instance isn't also setup to listen on port 1433. It will need a different port to listen on. What service pack is installed on the 2000 instance?

Denny
MCSA (2003) / MCDBA (SQL 2000)

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

http://www.mrdenny.com

(Not quite so old any more.)

 

[krios]

Denny,

I'm very new to this stuff, so I apologize in advance for all the questions!

I've been trying to stop the SQL 2005 instance, but i don't know how to restart the SQL 2000 instance. When i open the SQL Service Manager, i don't see the SQL 2000 server in the drop down menu. In the case that they are set up to listen on the same port, how would i find out and what should i change it to?


Thanks soooo much for the help! You don't know how long i've been trying to work this out! =P

Karina