SQL 2000 to SQL 2005: Where have all the old features gone?

Question

SQL 2000 to SQL 2005: Where have all the old features gone?

Viewing 10 posts - 31 through 39 (of 39 total)

You must be logged in to reply to this topic. Login to reply

icata Hall of Fame Points: 3176 More actions · Answer 1

I miss seeing easyly when a job had failed or a database been marked suspect because datafiles wasn't available

Alex A-400810 SSC Enthusiast Points: 113 More actions · Answer 2

Is this article joke? Everything mentioned exists in SQL 2000 ...xp_fixeddrives backupset ,restorehistory etc..I used those features since 2000 came out.

Mark Marinovic SSCrazy Points: 2472 More actions · Answer 3

Thankfully, SP2 (perhaps SP1 as well) has a host of reports that mimic the old TaskPad (which I used extensively). Just right-click on the database name, select 'Reports' --> Standard Reports. There are 17 to choose from, they're actually pretty nice. We (SQL Server community as a whole) must've got someone's ear at MS.

David Lu SSC Eights! Points: 882 More actions · Answer 4

100% agree. Event after using sql 2005 for around 8 months, still missing those 'lost features'.

Probably, some R&D people in MS decided to take them off since they are just from schools? just kidding

Philip Kelley SSCertifiable Points: 6351 More actions · Answer 5

The original point of the article was essentially about using the SQL Server 2005 client tools to manage SQL Server 2000 instances. Based on my experiences of the past few months, I say that doing this is a big mistake.

The SQL Server 2000 client tools were for all intents and purposes "second generation" -- 2.0 versions, revamped and revised from SQL Server 7.0. From what little I've heard, the SQL Server 2005 client tools were rewritten from the ground up in .Net 2.0 (which some say explains why they're so darn slow). Thus: on the one hand, no way could they recreate *everything* in their brand-new rewrite on the first go; on the other, maybe the original (C++?) coders cashed in their stock options, and MS had to recruit a fresh batch of college students.

[I'll site the interview by Rick Chapman with Joel Spolsky that he included in the back of his (Champamn's) book "In Search of Stupidity" for why the "rebuild from the gound up" trick is so very dangerous. Can't find it online, alas.]

Anyway, my point and strong recommendation is this: manage SQL 2005 instances with the SQL 2005 client tools, and manage the SQL 2000 instances with the SQL 2000 client tools. It makes no sense to manage 2000 in 2005 *if* you have no 2005 instances to support as well. (And if I did, I'd have both sets of client tools available, if only to maintain my sanity.)

Philip

htt SSCertifiable Points: 5242 More actions · Answer 6

so we are going backward using command lines instead of GUI? What a smart move by MS.

icata Hall of Fame Points: 3176 More actions · Answer 7

that would be quite true for rebuilding system databases

htt SSCertifiable Points: 5242 More actions · Answer 8

is this time for new customers to pick Oracle instead of MS SQL?

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 9

I don't know if it is THAT back to pick oracle over ss...

icata Hall of Fame Points: 3176 More actions · Answer 10

i think the application runs better and has much more features, but from admin point of view - day by day tasks I sometimes miss the EM