Re: SQL Patch not working on Professional

From: Richard Waymire [MS] (rwaymi@online.microsoft.com)
Date: 01/28/03


From: "Richard Waymire [MS]" <rwaymi@online.microsoft.com>
Date: Tue, 28 Jan 2003 11:52:52 -0800


Not sure I understand your question 100%.

To verify the engine version you should log in and run "select @@version"

or run

osql.exe -E -Q"select @@version" -Syourservername

If that's not

Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
 Dec 17 2002 14:22:05
 Copyright (c) 1988-2003 Microsoft Corporation
 Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 1)

(1 row(s) affected)

Then it needs to be updated. Notice on the last line mine says I'm running
the developer edition of SQL Server. If you see

Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
 Aug 6 2000 00:57:48
 Copyright (c) 1988-2000 Microsoft Corporation
 Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)

Then you have MSDE and need to download the MSDE patch.

--
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"mike" <mvalencia@tier3support.com> wrote in message
news:00c601c2c704$7773ce70$d6f82ecf@TK2MSFTNGXA13...
> If the user has the SP3 in the systray running and you run
> the information saying system info the version shows SQL
> 8.00.194 but I feel it may be MSDE 2.0 which patch would
> be needed for this?
>
> >-----Original Message-----
> >What edition of SQL Server and which SP3 are you using?
> I've also seen this
> >message when running the regular SP3 against an instance
> of MSDE - you need
> >the specific SP3 for MSDE as MSDE uses a different setup
> technology than SQL
> >Server if that's the case...
> >
> >--
> >Richard Waymire, MCSE, MCDBA
> >
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >"Mike" <mvalencia@tier3support.com> wrote in message
> >news:01a101c2c6f8$8ade03b0$d3f82ecf@TK2MSFTNGXA10...
> >> "SQL Server 2000 is not installed on this machine.
> Setup
> >> will now exit."
> >>
> >> Even though the SQL 2000 Server is running
> >>
> >> version 8.00.194
> >>
> >>
> >> >-----Original Message-----
> >> >no, it shoud work fine - what's the error message being
> >> returned?
> >> >
> >> >--
> >> >Richard Waymire, MCSE, MCDBA
> >> >
> >> >This posting is provided "AS IS" with no warranties,
> and
> >> confers no rights.
> >> >"Mike" <mvalencia@tier3supportt.com> wrote in message
> >> >news:06bc01c2c6f1$b6341600$8af82ecf@TK2MSFTNGXA03...
> >> >> Is there a reason a customer cannot run the SP3 SQL
> >> patch
> >> >> on a Win2K professional environment.
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >


Relevant Pages

  • Re: What version of SQL is on SBS R2 Standard and can I use it?
    ... I followed your instructions and successfully installed SQL Express, ... During the application install the applicaton didn't reconize the default ... SQLEXPRESS and two MSDE instances. ... super administrative purposed within SQL Server and is not the same as the ...
    (microsoft.public.windows.server.sbs)
  • Re: What version of SQL is on SBS R2 Standard and can I use it?
    ... named instance but default for SQL Express). ... A user level account works ... super administrative purposed within SQL Server and is not the same as the ... you can have MSDE and 2005 Express ...
    (microsoft.public.windows.server.sbs)
  • Re: 1 server 2 SQL apps
    ... Does it make sense in this situation to use MSDE 2000 SP3, ... MSDE has a limitation of 2 GB per database as well as you will not get the ... clients lke query analyzer, Enterprise manager. ... Best option for you might be, Install a default installation of SQL server ...
    (microsoft.public.sqlserver.server)
  • Re: Renaming Computer Running SQL or MSDE
    ... I've only seen problems with SQL Server 7 (ie and MSDE v1). ... >> In my experience when you rename a computer ...
    (microsoft.public.sqlserver.msde)
  • Re: SP3 for MSDE 2000
    ... instances of SQL Server and MSDE. ... International customers should call their local subsidiaries. ... > Better than that - I just found out that the default new instance that SP3 ...
    (microsoft.public.sqlserver.security)