Is this a regional error? - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

Site Related Forums

The Yak Corral

Is this a regional error?

Author

Topic

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2008-04-15 : 09:19:49

I helped with a what seemed a fairly simple query.
But now it seems that some people do not get the correct result, not even with supplied sample data.

The topic is found here http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=100988
Who else do get correct result and who get incorrect result?

Post in that topic your result of the supplied sample data and code and also which edition and version of sql server you are using.
If if this is a collation problem (don't ask me how it could be), also provide information about your regional area.

Thanks,

//Peso

E 12°55'05.25"
N 56°04'39.16"

madhivanan
Premature Yak Congratulator

22864 Posts

Posted - 2008-04-15 : 09:36:07

quote:
Originally posted by Peso

I helped with a what seemed a fairly simple query.
But now it seems that some people do not get the correct result, not even with supplied sample data.

The topic is found here http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=100988
Who else do get correct result and who get incorrect result?

Post in that topic your result of the supplied sample data and code and also which edition and version of sql server you are using.
If if this is a collation problem (don't ask me how it could be), also provide information about your regional area.

Thanks,

//Peso

E 12°55'05.25"
N 56°04'39.16"

It is another behavioural change in SQL Server 2005

Madhivanan

Failing to plan is Planning to fail

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2008-04-15 : 09:50:45

quote:
Originally posted by madhivanan

It is becuase you are using SQL Server 2000 and Peso is using SQL Server 2005

You're funny now, Madhi?

I get correct result on all our server, ranging from SQL 2000 to SQL 2008.

E 12°55'05.25"
N 56°04'39.16"

madhivanan
Premature Yak Congratulator

22864 Posts

Posted - 2008-04-15 : 09:54:07

quote:
Originally posted by Peso

quote:
Originally posted by madhivanan

It is becuase you are using SQL Server 2000 and Peso is using SQL Server 2005

You're funny now, Madhi?

I get correct result on all our server, ranging from SQL 2000 to SQL 2008.

E 12°55'05.25"
N 56°04'39.16"

No. Didnt you come across the same problem with the use of derived table sometimes back?

Madhivanan

Failing to plan is Planning to fail

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2008-04-15 : 10:08:35

Only when putting a WHERE filter on them, then the query engine bypasses some logic.
And that was SQL Server 2005 bringing back strange results, not SQL Server 2000 as in the topic above.

I have tested on these configurations now and all bring back correct result

Microsoft SQL Server 2000 -  8.00.2039		Standard Edition
Microsoft SQL Server 2005 -  9.00.3215.00	Developer Edition
Microsoft SQL Server 2005 -  9.00.3054.00	Standard Edition
Microsoft SQL Server 2008 - 10.0.1300.13	Developer Edition

E 12°55'05.25"
N 56°04'39.16"

RickD
Slow But Sure Yak Herding Master

3608 Posts

Posted - 2008-04-15 : 10:38:02

Peter - I get the same result as you.

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2008-04-15 : 10:44:45

It seems OP used RTM version of SQL Server 2000 MSDE to get the unexpected behaviour.

E 12°55'05.25"
N 56°04'39.16"

tkizer
Almighty SQL Goddess

38200 Posts