November 11, 2011 at 4:55 am
If you can resolve the problem by moving your WHERE clause, though, is it really that big of a deal?
I personally think you should upgrade to SP4, BTW. I'm just playing devil's advocate with the above question.
November 11, 2011 at 4:58 am
Brandie Tarvin (11/11/2011)
If you can resolve the problem by moving your WHERE clause, though, is it really that big of a deal?I personally think you should upgrade to SP4, BTW. I'm just playing devil's advocate with the above question.
I just did update to SP4 on the test server. Still not resolved.
I'll try the same code on my other versions.
I keep on going because I don't want bugs in "my" product :cool:.
November 11, 2011 at 5:02 am
Cancel that... seems like the upgrade failed.
Who said there was no risk? :hehe:
November 11, 2011 at 5:07 am
Ninja's_RGR'us (11/11/2011)
Cancel that... seems like the upgrade failed.Who said there was no risk? :hehe:
No-one - the phrase was "pretty small risk".
November 11, 2011 at 5:09 am
SQL Kiwi (11/11/2011)
Ninja's_RGR'us (11/11/2011)
Cancel that... seems like the upgrade failed.Who said there was no risk? :hehe:
No-one - the phrase was "pretty small risk".
It works 99.99% of the time.
...well, okay. It works 97% of the time.
...Oh, stop looking at me like that. I swear, it works 80% of the time...
...at least 50% of the time. Honest...
Okay, already! You've got me. It works some of the time. At least 3 times out of ... well, a lot...
I'm shutting up now.
November 11, 2011 at 5:11 am
SQL Kiwi (11/11/2011)
Ninja's_RGR'us (11/11/2011)
Cancel that... seems like the upgrade failed.Who said there was no risk? :hehe:
No-one - the phrase was "pretty small risk".
I know, hence TEST server :-D.
Nothing corrupt, just failed... trying again.
November 11, 2011 at 5:18 am
Ok, I'm just playing with ya'll.
id10t error.
The SSMS is installed in english but part ofthe install is done in french.
I don't even want to know how they managed that.
Trying again the test in 10 minutes once THAT upgrade works. Hopefully 50% of the time is enough :-D.
November 11, 2011 at 5:34 am
Ninja's_RGR'us (11/11/2011)
Brandie Tarvin (11/11/2011)
If you can resolve the problem by moving your WHERE clause, though, is it really that big of a deal?I personally think you should upgrade to SP4, BTW. I'm just playing devil's advocate with the above question.
I just did update to SP4 on the test server. Still not resolved.
I'll try the same code on my other versions.
I keep on going because I don't want bugs in "my" product :cool:.
Repeat that... same results with =>
SELECT @@VERSION
--Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86) Dec 10 2010 10:56:29 Copyright (c) 1988-2005
--Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Back to trying with other versions (our admindoesn't use non SP updates)!
November 11, 2011 at 6:16 am
I've shrunk down the db so tha I can move it around more easily and use it on express.
The bug seems gone in express R2 and Denali CTP3.
So I'll call this closed. For real this time!
Thanks again y'all.
November 11, 2011 at 6:24 am
Glad you found a solution, even if it doesn't help you right now.
November 11, 2011 at 6:26 am
Brandie Tarvin (11/11/2011)
Glad you found a solution, even if it doesn't help you right now.
I had the solution, I wanted to know if it was a known bug before wasting 4 hours to post the connect item for it :-P.
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply