SQL versions

[SQLScholar]

hey all,

I am a tad confused (no change there). At each SQL server we have i ran the below code

select @@VERSION
 
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

SITE 1
R3 - running Windows Server 2003 R1


Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )

8.00.2039,SP4,Standard Edition

SITE 2 - Running Windows Server 2000

Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

8.00.2039,SP4,Standard Edition

SITE 3 - Running Windows Server 2003 R2

Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

8.00.2039,SP4,Standard Edition

SITE 4 - Running Windows Server 2000

Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

8.00.760,SP3,Standard Edition

Ok - so my main question is why the difference in @@Version and the other code? We seem to be having odd compatability issues with our software and site 1.

Any clues to these differences is really appreciated.

Dan





----------------------------------------
Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind - Dr. Seuss

Computer Science is no more about computers than astronomy is about telescopes - EW Dijkstra
----------------------------------------

 

[ptheriault]

Site 1 appears to be the only site running Windows Server 2003 R1. Have you tested your software on that release of windows?

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[gmmastros]

Try running this on each server.

[tt][blue]Select ServerProperty('collation')[/blue][/tt]

As Paul said, it could be an operating system compatibility issue, but I would think the problem has more to do with the configuration settings instead. And, in my experience, collation settings are the most problematic. Good luck.

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[SQLScholar]

ptheriault,

Yes that is whats happening. Site one is having an issue on testing, we cant work out why?

Does anyone know what the difference will be?

Gmmastros,

Here are the results.

Site1

Latin1_General_CI_AS

Site2

SQL_Latin1_General_CP1_CI_AS

Site3

Latin1_General_CI_AS

Site4

Latin1_General_CI_AS

So it seems that the only one out of the set, is not the one having problems.

any other ideas?

Dan

----------------------------------------
Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind - Dr. Seuss

Computer Science is no more about computers than astronomy is about telescopes - EW Dijkstra
----------------------------------------

 

[ptheriault]

George,
great idea. I didn't even think about the collation.

Dan,
Can you upgrade site 1 to R2?

What is the error that you are getting?

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[SQLScholar]

No unfortunately we dont have a spare 2003 R2 licence.

Issue is shown here by a guy i work with:

http://www.tek-tips.com/viewthread.cfm?qid=1321565

Dan

----------------------------------------
Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind - Dr. Seuss

Computer Science is no more about computers than astronomy is about telescopes - EW Dijkstra
----------------------------------------

 

[ptheriault]

Do you have another test box with R1 on it? Is this just a test environment? What is the service pack of your MDAC 2.8 install. Can you upgrade your MDAC to 2.8 sp2? Here is a link to check your MDAC version.

http://www.microsoft.com/downloads/...f6-4a21-4b43-bf53-14332ef092c9&DisplayLang=en

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[SQLScholar]

ptheriault,

No we dont have any other R1`s.

Yes it is a test environment (our development one actually :-(

It was MDAC 2.8 RTM - so we updated it to 2.8SP2 and its still doing it.

any other ideas?

Dan

----------------------------------------
Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind - Dr. Seuss

Computer Science is no more about computers than astronomy is about telescopes - EW Dijkstra
----------------------------------------

 

[ptheriault]

Sorry Dan,
The only suggestion that I have now is to upgrade to R2. You know it will work there.
We have a standard config for all our servers. They must all be at the same patch level.
You could also implemant a work around.
Check the server version and based on the version execute the code that will work.

Sorry I can't offer any better advice.

- Paul
- If at first you don't succeed, find out if the loser gets anything.