?

Log in

No account? Create an account
SQL Server 2005 - The Cover Story
October 2013
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
 
Wed, Mar. 1st, 2006 03:01 pm
SQL Server 2005

I just today got SQL Server 2005 Trial working on SAPPHIRE. It was my first opportunity to test-drive the new system. The installer is a bit counter-intuitive, being rather different than 2000's, but other than that it has some nice features, such as explicit scans of prerequisites and other checks. The Enterprise Manager has been replaced with the SQL Server Management Studio, which definitely has a very .NET-ty feel to it, and changes the way information is presented quite a bit. It still has the plastic look-and-feel of XP, but also clearly has significantly more thrust behind it than 2000 did. Most glaring for me is the absence of DTS, which I virtually made a career out of knowing backwards and forwards. In its place stands Analysis Services, which, as far as I've read, are geared much more toward the business user than the IT user. I'm still analyzing the AS systems, but it looks like this is a dramatically different paradigm from DTS's technically straight-forward manipulation of data sources. Interestingly enough, there are now tables referring to something called a "DTS 9.0", but the help files still tell you to use Enterprise Manager to edit DTS Packages.

Also poking up from behind the new facade is a brand-new ODBC interface. It seems OLEDB is no longer supported under SQL 2005, and there's not apparent option to make it backwards compatible, meaning that any app that was trusting to connect to Microsoft SQL 2005 using the Microsoft SQL 2000 connection string will have to be maintained. Not exactly a fatal flaw, but a subtle annoyance that's sure to raise some eyebrows and slow the deployment of 2005 to legacy environments. It also means that Enterprise Manager won't like SQL 9.0, but on the plus side, the Management Studio seems more than happy to connect to older instances.

Oh well. The .NET era has been one of dramatic redesigns of products that hadn't changed much in metaphor and interface since Windows 3.1. Looks like its time for the SQL Administrators to jump on the bandwagon.

Tags: , ,

6CommentReplyShare

purly
purly
...
Wed, Mar. 1st, 2006 09:48 pm (UTC)

So apps made to connect to any sql environ via odbc can't now?


ReplyThread
bronzite
bronzite
Robert Bronzite
Wed, Mar. 1st, 2006 10:06 pm (UTC)

They can -- they just need the new set of ODBC drivers for SQL 2005. The old OLEDB drivers don't work anymore.


ReplyThread Parent
mikecap
mikecap
Mike Caprio
Wed, Mar. 1st, 2006 10:30 pm (UTC)

We are also playing with it here. We haven't had time to do much lately though because we're right now at this very moment putting out the new DMT.


ReplyThread
bronzite
bronzite
Robert Bronzite
Wed, Mar. 1st, 2006 10:39 pm (UTC)

Yeah, as far as I can tell this new system will have some very profound implications for basic methodology, but they're not paying me to solve that problem. (yet).


ReplyThread Parent
mikecap
mikecap
Mike Caprio
Wed, Mar. 1st, 2006 10:44 pm (UTC)

It's going to be a long while before we support any of it. Six months plus at least.


ReplyThread Parent
petercooperjr
petercooperjr
Peter Cooper Jr.
Fri, Mar. 3rd, 2006 10:46 pm (UTC)

I think you're crazy. SQL 2005 supports OLE DB and has DTS just fine... Where in the world are you getting your information from?


ReplyThread