| Author |
Topic |
|
silas2
Yak Posting Veteran
65 Posts |
 Posted - 2005-10-20 : 14:09:27
|
| I really don't understand this, in an attempt to upgrade/install SP3a, I download the file sql2kdesksp3.exe, which from the documentation, you can either use for upgrading or new installs. I run a new install; in the new instance, I execute "select @@version" and get "Service Pack 1"?? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-10-20 : 14:11:03
|
| Could you post exactly what @@VERSION shows? I believe you are posting the OS version and not the SQL Server version.Tara |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-10-20 : 14:11:10
|
| it is talking about the OS you installed it onto. What is the build number for SQL Server. Should be 760.-ec |
|
|
|
silas2
Yak Posting Veteran
65 Posts |
Posted - 2005-10-20 : 14:28:43
|
| Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 1) |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
silas2
Yak Posting Veteran
65 Posts |
Posted - 2005-10-20 : 14:48:08
|
| That's a shame, it was my last diagnostic avenue! The problem I was trying to resolve was that I couldn't connect to a named instance from a client thru TCP/IP, I can connect to the default instance. I discovered that port 1434 udp, when queried by portqry should list the server instances, but portqry comes back with FILTERED, which I guess means that nothing's listening (or replying). I've searched everywhere, but I can't find a diagnostic route to go down if you get this, except "are you sure its SP3"?. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-10-20 : 17:03:32
|
quote:
Originally posted by silas2
That's a shame, it was my last diagnostic avenue! The problem I was trying to resolve was that I couldn't connect to a named instance from a client thru TCP/IP, I can connect to the default instance. I discovered that port 1434 udp, when queried by portqry should list the server instances, but portqry comes back with FILTERED, which I guess means that nothing's listening (or replying). I've searched everywhere, but I can't find a diagnostic route to go down if you get this, except "are you sure its SP3"?.
if port 1434 is filtered then you will need to create an alias in the client configuration tool (cliconfg from the command prompt). When creating the alias, uncheck the checkbox for dynamically determining the port number and type in the port manually.To determine the port for your instance you need to run the server network tool. Good luck.-ec |
|
|
|
silas2
Yak Posting Veteran
65 Posts |
Posted - 2005-10-21 : 05:02:39
|
| I had some problem understanding these ports, my understanding is that M'soft booked 1433 for SQL Server, but no other; only one instance can use one port at a time, but every time you install a new instance, it uses 1433 as the default port(?) Therefore you can have loads of instances using 1433 as the default port. Are you supposed to "hard wire" a named instance to a port of your choice using the "think of a number" algorithm? |
|
|
|
silas2
Yak Posting Veteran
65 Posts |
Posted - 2005-10-21 : 11:16:38
|
| I sorted it, blimey, take me back to file sharing and Access! |
|
|
|
|
SP3a installs SP1