SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The Easy Poll


The Easy Poll

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (249K reputation)SSC Guru (249K reputation)SSC Guru (249K reputation)SSC Guru (249K reputation)SSC Guru (249K reputation)SSC Guru (249K reputation)SSC Guru (249K reputation)SSC Guru (249K reputation)

Group: Administrators
Points: 249956 Visits: 19813
Comments posted to this topic are about the item The Easy Poll

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Japie Botma
Japie Botma
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1064 Visits: 369
I want SP5 for SQL Server 2000. (Dont care about SQL 2005. I am waiting for SQL 2008, although already legal on 2005)

5ilverFox
Consulting DBA
South Africa
GilaMonster
GilaMonster
SSC Guru
SSC Guru (416K reputation)SSC Guru (416K reputation)SSC Guru (416K reputation)SSC Guru (416K reputation)SSC Guru (416K reputation)SSC Guru (416K reputation)SSC Guru (416K reputation)SSC Guru (416K reputation)

Group: General Forum Members
Points: 416242 Visits: 47141
Give me SP3!

We're currently pushing to get the 5th cumulative update on one of our servers (cause we keep running into a problem that was fixed in SP2 and fixed again in a patch that made it into CU 4)

We're running into reluctance because 'It's not a service pack. We should wait for the next service pack'. Meanwhile I'm flushing out the token cache every 3 hours...

SP5 for 2000, not so much. All my remaining SQL 2000 servers are vendor apps. If they don't say we can patch/upgrade, we're not allowed to. They haven't allowed an upgrade to SQL 2005, so I doubt they'll test a SP5.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Dan Jones-279024
Dan Jones-279024
Mr or Mrs. 500
Mr or Mrs. 500 (584 reputation)Mr or Mrs. 500 (584 reputation)Mr or Mrs. 500 (584 reputation)Mr or Mrs. 500 (584 reputation)Mr or Mrs. 500 (584 reputation)Mr or Mrs. 500 (584 reputation)Mr or Mrs. 500 (584 reputation)Mr or Mrs. 500 (584 reputation)

Group: General Forum Members
Points: 584 Visits: 87
I think the interesting question is: what do you want in SQL2K5 SP3?
P Jones
P Jones
SSCarpal Tunnel
SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)

Group: General Forum Members
Points: 4775 Visits: 1534
Absolutely, definitly, no question we want SP for both and regular SP for supported products.
majorbloodnock
majorbloodnock
Hall of Fame
Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)

Group: General Forum Members
Points: 3619 Visits: 3064
My answer's rather more basic. I want my SQL servers to be reasonably bug-free and secure. I'm not too concerned about how that's achieved. If Microsoft wanted to rebadge their last cumulative update as "Service Pack 3", I wouldn't be any the wiser, but would be just as happy. As long as I have the mechanisms I need AND those mechanisms are reasonably easy to administer, that'll do it for me.

Semper in excretia, sumus solum profundum variat
IceDread
IceDread
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1523 Visits: 1145
My answere to the big Q is of courses YES I want an SP3.
Jamie Batiste
Jamie Batiste
Right there with Babe
Right there with Babe (762 reputation)Right there with Babe (762 reputation)Right there with Babe (762 reputation)Right there with Babe (762 reputation)Right there with Babe (762 reputation)Right there with Babe (762 reputation)Right there with Babe (762 reputation)Right there with Babe (762 reputation)

Group: General Forum Members
Points: 762 Visits: 250
As a developer I want a stable platform to work off.

Most MS customers don't necessarily understand what goes in to a service pack or update - especially those that outsource IT/small number of staff etc, but to me having a more rigorously tested app with a complete roll up of all issues to date X is a plus.

We generally don't go to the next product unless SP1 is out and tested. I went Vista on Feb 1 2007 and am still getting bitten by issues...so can't develop from that machine yet! Do I hear an XP service pack anyone?

2000 SP5? Yes - only 10% of our customers are on anything else. Why change your workhorse when it still gives you what you need?

2005 SP3? Thats a given surely!
ALZDBA
ALZDBA
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53357 Visits: 9117
Oh certainly a huge yes regarding SP-release Exclamation Mark

Why, because IMHO a SP is considered to be a stable release, tested well by the manufacturer. Certainly worth a general test and go.

A cumulative update is just a new package of hotfixes, designed for certain issues, so IMO not _that_ stable for us (systems managers) to give it a general test and go.

Also with CUs the frequency is to high to set up a release cycle every time.

After all, we have to determine which version of the software we will install by default when a new instance is being asked for.
For now that is set to SQL2005 SP2 + CU4.
But the active production instances are not yet being upgraded with CU4. (they are still on CU2)

Johan


Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere w00t

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


press F1 for solution, press shift+F1 for urgent solution :-D


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me Alien but most of the time this is me Hehe
SQLPhil
SQLPhil
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2386 Visits: 740
I'd agree with Alzdba.

We're rolling out SQL 2005 at the moment mainly it's had 2 service packs and for me this is an indicator that the manufacturer's put some effort into ensuring that all those initial bugs have been ironed out. I haven't bothered with the cumulative updates so far because I'm a bit nervous about applying something that comes with a disclaimer saying:

"This cumulative update package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2005 service pack that contains the hotfixes in this cumulative update package"

So yeah - I'd like SP3 - please.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search