I have two developers using Windows 2003 Web Edition to develop web
applications. They are not being allowed to install the SQL Server Manager
client tools. Why would Microsoft introduce restrictions on the SQL Server
*client* administration tools in the Web Edition of Windows 2003? How can
it not be clear to anyone that the SQL Server client tools are needed for
development of *web* applications?!

Whatever licensing theory they are applying here is very obscure.

--
Will

Re: Cannot Install SQL Server Client Admin Tools on Windows 2003 Web Edition? by David

David
Tue Feb 20 02:12:05 CST 2007

I think the Web Edition does not allow one to install SQL, period,
client or server.

There probably was some problem distinguishing between SQL setup
installing server or client, and since SQL server is not allowed on
Web Edition, the client probably got inadvertently banned as well.

You make a good point (there are many other bizarre restrictions in
the Web Edition which makes it all but useless for anything other than
a web server farm "clone").

http://technet2.microsoft.com/WindowsServer/en/library/81999f39-41e9-4388-8d7d-7430ec4cc4221033.mspx?mfr=true

Personally, for web-app development, I would use a XP Pro x64 Edition
because you get all the Client benefits plus IIS6 locally on x64. It's
just better than Web Edition.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Feb 19, 8:29 pm, "Will" <westes-...@noemail.nospam> wrote:
> I have two developers using Windows 2003 Web Edition to develop web
> applications. They are not being allowed to install the SQL Server Manager
> client tools. Why would Microsoft introduce restrictions on the SQL Server
> *client* administration tools in the Web Edition of Windows 2003? How can
> it not be clear to anyone that the SQL Server client tools are needed for
> development of *web* applications?!
>
> Whatever licensing theory they are applying here is very obscure.
>
> --
> Will



Re: Cannot Install SQL Server Client Admin Tools on Windows 2003 Web Edition? by Will

Will
Tue Feb 20 22:05:56 CST 2007

"David Wang" <w3.4you@gmail.com> wrote in message
news:1171959125.750537.59600@q2g2000cwa.googlegroups.com...
> I think the Web Edition does not allow one to install SQL, period,
> client or server.

Which makes Web Edition of very questionable worth. I'm also wondering if
Microsoft is thinking clearly on that. The web developer who cannot use
Web Edition to develop applications to be deployed to Web Edition probably
ends up using Windows XP. That's less money for Microsoft.


> There probably was some problem distinguishing between SQL setup
> installing server or client, and since SQL server is not allowed on
> Web Edition, the client probably got inadvertently banned as well.

Probably, but that's a primary use application so you would think they would
have addressed it by now in a hot fix.


> Personally, for web-app development, I would use a XP Pro x64 Edition
> because you get all the Client benefits plus IIS6 locally on x64. It's
> just better than Web Edition.

But then again you get lots of weird incompatibilities with win32
applications as well, missing drivers, etc. Leading edge, bleeding edge,
etc.

With Windows Server 2003 we were getting disk mirroring, RDP as a separate
background activity from the console login, etc.

--
Will




Re: Cannot Install SQL Server Client Admin Tools on Windows 2003 Web Edition? by David

David
Wed Feb 21 05:49:32 CST 2007

On Feb 20, 8:05 pm, "Will" <westes-...@noemail.nospam> wrote:
> "David Wang" <w3.4...@gmail.com> wrote in message
>
> news:1171959125.750537.59600@q2g2000cwa.googlegroups.com...
>
> > I think the Web Edition does not allow one to install SQL, period,
> > client or server.
>
> Which makes Web Edition of very questionable worth. I'm also wondering if
> Microsoft is thinking clearly on that. The web developer who cannot use
> Web Edition to develop applications to be deployed to Web Edition probably
> ends up using Windows XP. That's less money for Microsoft.
>
> > There probably was some problem distinguishing between SQL setup
> > installing server or client, and since SQL server is not allowed on
> > Web Edition, the client probably got inadvertently banned as well.
>
> Probably, but that's a primary use application so you would think they would
> have addressed it by now in a hot fix.
>
> > Personally, for web-app development, I would use a XP Pro x64 Edition
> > because you get all the Client benefits plus IIS6 locally on x64. It's
> > just better than Web Edition.
>





> But then again you get lots of weird
> incompatibilities with win32 applications
> as well, missing drivers, etc.

Are you just repeating this or do you have concrete evidence for the
specific web-dev applications that you are interested in?

I have no problems with any of my development-related or System tools
on x64, and even if it does, I can find an x64 version.

> With Windows Server 2003 we were getting
> disk mirroring, RDP as a separate
> background activity from the console login, etc.

XP Pro x64 is based off of the Windows Server 2003 codebase so you
have the same Remote Desktop engine.

Software RAID can be had on XP Pro if you are clever...

I'm simply saying that from my perspective and experience, x64 is a
viable and future-proof dev platform. The list of x64 drivers, while
not exhaustive, is certainly more than feasible and growing,
especially if you just grab any stock Dell x64 machine that already
has it all figured out. Driver issues depend completely on hardware,
and for development purposes, fancy/legacy hardware should not be
involved.

Add on Visual Studio 2005 x64, Microsoft Debugging Toolkit x64,
Microsoft Office 2007 which runs on x64, your favorite web browser,
text editor, and Systems tools... and I find that most everything I
need works perfectly fine on x64.

Anyways, everyone has their opinion on this subject, but for certain
SQL isn't installable on Web Edition and I highly doubt it will ever
change at this point.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//