Discussion:
Does WSUS 3 support SQL Express SP2?
(too old to reply)
Michael Kincaid
2007-05-01 22:42:02 UTC
Permalink
I'm trying to install WSUS 3.0 on a server with a running instance (default
name) of SQL Express 2005 SP2 w/Advanced Services, and on "Database
Options," "Use an existing database server on this computer" is grayed out
and if I enter myserver\MSSQLSERVER as the remote instance name, I get "The
specified service does not exist as an installed service".

The WSUS 3 documentation doesn't explicitly address SP2, as far as I can
tell (only names SP1 as a requirement). Neither does it explicitly address
SQL Express, so I'd assumed that was included under the umbrella of SQL
Server 2005 support, but perhaps I have assumed incorrectly.

I do understand that the Windows Internal Database circumvents some of the
limits that apply with SQL Express, but I don't think these limits will be a
problem in our environment, and so I prefer the manageability of the Express
instance.

Any thoughts/experiences with this pairing, or steps I might take to find
out what's wrong with the instance I have running? Am I missing something
obvious?

thanks,
--Michael
Lawrence Garvin (MVP)
2007-05-01 23:05:58 UTC
Permalink
Post by Michael Kincaid
I'm trying to install WSUS 3.0 on a server with a running instance
(default name) of SQL Express 2005 SP2 w/Advanced Services, and on
"Database Options," "Use an existing database server on this computer" is
grayed out and if I enter myserver\MSSQLSERVER as the remote instance
name, I get "The specified service does not exist as an installed
service".
The installer is looking for an "existing database server" on the default
instance. Most likely your SQL Express has been installed on instance name
SQLEXPRESS, making it invisible to the WSUS installer.
Post by Michael Kincaid
The WSUS 3 documentation doesn't explicitly address SP2, as far as I can
tell (only names SP1 as a requirement). Neither does it explicitly address
SQL Express, so I'd assumed that was included under the umbrella of SQL
Server 2005 support, but perhaps I have assumed incorrectly.
There's the potential for the same type of issues with the SQL 2005 SP1/SP2
scenario as there were sometimes observed with the SQL 2000 SP3/SP4
scenario. WSUSv2 didn't always behave well when installed to SQL 2000 SP4; I
wouldn't be entirely surprised (and we saw some in the beta) if there are
issues installing WSUSv3 on SQL 2005 SP2.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
....
Michael Kincaid
2007-05-01 23:26:57 UTC
Permalink
Thanks for the quick response!
Post by Lawrence Garvin (MVP)
The installer is looking for an "existing database server" on the default
instance. Most likely your SQL Express has been installed on instance name
SQLEXPRESS, making it invisible to the WSUS installer.
I did think of that, but using myserver\SQLEXPRESS as the instance doesn't
work either.
Post by Lawrence Garvin (MVP)
There's the potential for the same type of issues with the SQL 2005
SP1/SP2 scenario as there were sometimes observed with the SQL 2000
SP3/SP4 scenario. WSUSv2 didn't always behave well when installed to SQL
2000 SP4; I wouldn't be entirely surprised (and we saw some in the beta)
if there are issues installing WSUSv3 on SQL 2005 SP2.
Upon reading the release notes more carefully, I notice now that SQL 2005
SP2 is required on Longhorn, but I suppose that doesn't necessarily make it
supported on Win2k3.

It sounds like for this scenario it may be a better bet to just abandon
Express and go with WID/SSEE?
Bastian Haas
2007-05-02 13:56:01 UTC
Permalink
Post by Michael Kincaid
It sounds like for this scenario it may be a better bet to just abandon
Express and go with WID/SSEE?
The only thing I can say regarding to your question is that I successfully
installed WSUS 3 this morning using a SQL 2005 Express SP2 database. More
precisely on a server with three SQL Express instances.
Michael Kincaid
2007-05-02 21:55:26 UTC
Permalink
Post by Bastian Haas
Post by Michael Kincaid
It sounds like for this scenario it may be a better bet to just abandon
Express and go with WID/SSEE?
The only thing I can say regarding to your question is that I successfully
installed WSUS 3 this morning using a SQL 2005 Express SP2 database. More
precisely on a server with three SQL Express instances.
Was it recognized as an "existing database server" or did you have to enter
the instance name manually?
Bastian Haas
2007-05-03 15:44:02 UTC
Permalink
Post by Michael Kincaid
Was it recognized as an "existing database server" or did you have to enter
the instance name manually?
It was recognized and could be chosed as an "existing database server". It
listed all three instances and I simply selected the one I hat just created
before WSUS setup.
unknown
2010-01-08 13:11:34 UTC
Permalink
Hi
I was reading your comments with regards to choose existing database server instead of WID,
I have tried, but keep on saying "not installed as a service"
please advice me how to do it, i have installed SQL Express and wanted to use it for WSUS:
I have tried both names like \\servername\sqlexpress but not winning

please assist



BastianHaa wrote:

It was recognized and could be chosed as an "existing database server".
03-May-07

It was recognized and could be chosed as an "existing database server". I
listed all three instances and I simply selected the one I hat just create
before WSUS setup.

Previous Posts In This Thread:

On Tuesday, May 01, 2007 6:42 PM
Michael Kincaid wrote:

Does WSUS 3 support SQL Express SP2?
I'm trying to install WSUS 3.0 on a server with a running instance (default
name) of SQL Express 2005 SP2 w/Advanced Services, and on "Database
Options," "Use an existing database server on this computer" is grayed out
and if I enter myserver\MSSQLSERVER as the remote instance name, I get "The
specified service does not exist as an installed service"

The WSUS 3 documentation doesn't explicitly address SP2, as far as I can
tell (only names SP1 as a requirement). Neither does it explicitly address
SQL Express, so I'd assumed that was included under the umbrella of SQL
Server 2005 support, but perhaps I have assumed incorrectly

I do understand that the Windows Internal Database circumvents some of the
limits that apply with SQL Express, but I don't think these limits will be a
problem in our environment, and so I prefer the manageability of the Express
instance

Any thoughts/experiences with this pairing, or steps I might take to find
out what's wrong with the instance I have running? Am I missing something
obvious

thanks
--Michael

On Tuesday, May 01, 2007 7:05 PM
Lawrence Garvin \(MVP\) wrote:

Re: Does WSUS 3 support SQL Express SP2?
"Michael Kincaid" <***@luidia.com> wrote in message news:F9A51914-96F8-48B5-B7F4-***@microsoft.com..

The installer is looking for an "existing database server" on the default
instance. Most likely your SQL Express has been installed on instance name
SQLEXPRESS, making it invisible to the WSUS installer

There's the potential for the same type of issues with the SQL 2005 SP1/SP2
scenario as there were sometimes observed with the SQL 2000 SP3/SP4
scenario. WSUSv2 didn't always behave well when installed to SQL 2000 SP4; I
wouldn't be entirely surprised (and we saw some in the beta) if there are
issues installing WSUSv3 on SQL 2005 SP2

--
Lawrence Garvin, M.S., MCTS, MC
Independent WSUS Evangelis
MVP-Software Distribution (2005-2007
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36

Everything you need for WSUS is a
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.msp

And, almost everything else is a
http://wsusinfo.onsitechsolutions.co
....

On Tuesday, May 01, 2007 7:26 PM
Michael Kincaid wrote:

Thanks for the quick response!
Thanks for the quick response

"Lawrence Garvin (MVP)" <***@community.nospam> wrote in message news:***@TK2MSFTNGP06.phx.gbl..

I did think of that, but using myserver\SQLEXPRESS as the instance doesn't
work either

Upon reading the release notes more carefully, I notice now that SQL 2005
SP2 is required on Longhorn, but I suppose that doesn't necessarily make it
supported on Win2k3

It sounds like for this scenario it may be a better bet to just abandon
Express and go with WID/SSEE?

On Wednesday, May 02, 2007 9:56 AM
BastianHaa wrote:

Re: Does WSUS 3 support SQL Express SP2?
"Michael Kincaid" wrote

The only thing I can say regarding to your question is that I successfully
installed WSUS 3 this morning using a SQL 2005 Express SP2 database. More
precisely on a server with three SQL Express instances.

On Wednesday, May 02, 2007 5:55 PM
Michael Kincaid wrote:

Re: Does WSUS 3 support SQL Express SP2?
Was it recognized as an "existing database server" or did you have to ente
the instance name manually?

On Thursday, May 03, 2007 11:44 AM
BastianHaa wrote:

It was recognized and could be chosed as an "existing database server".
It was recognized and could be chosed as an "existing database server". It
listed all three instances and I simply selected the one I hat just created
before WSUS setup.


Submitted via EggHeadCafe - Software Developer Portal of Choice
The Guru's Guide To Transact-SQL
http://www.eggheadcafe.com/tutorials/aspnet/7ce4ff7d-89c9-4be6-90c3-29efb48e739c/the-gurus-guide-to-trans.aspx
Loading...