Query Analyzer on 2003 WE

[rdhatt]

Hi -

The developers in my company are all switching to Windows 2003 Web
Edition for their dev machines so they can better target the platform.
Unfortunately we have discovered that we unable to install the SQL
Server tools due (Query Analyzer, Profiler, etc) to the restriction
that SQL Server is not allowed. The devs run their databases on a
centeral server. Is there any workaround[1] to allow just the tools on
2003 WE?

Thanks!

[1] Installing another version of 2003 (Standard, Enterprise) is not an
good option since a) that isn't what our production servers run b) the
admin doesn't want to give the devs the ability to do something stupid,
like turn their desktop into a domain controller.

[Simon Hayes]

Since Web Edition is specifically intended as a limited platform for
running a web server, I'm not sure why you would want to use it as a
development workstation OS (which is what I understood you to mean).

The MS web page says that WE "can be used solely to deploy Web pages,
Web sites, Web applications, and Web services", which suggests that
using it for other purposes may be against the license agreement in any
case.

Why not simply have a few installations of Web Edition available which
the developers deploy their code to for testing? Or perhaps use VMWare
to allow them to run it on their desktops in a virtual session?

Simon

[rdhatt]

> The MS web page says that WE "can be used solely to deploy Web pages,

Web sites, Web applications, and Web services", which suggests that
using it for other purposes may be against the license agreement in any case.
Hmm...interesti ng point. These installs were going to come from the
dev's MSDN subscriptions which gives them such thing for development.
I can follow up the MSDN people on this.
Why not simply have a few installations of Web Edition available which the developers deploy their code to for testing? Or perhaps use VMWare to allow them to run it on their desktops in a virtual session?

For the simple reason that it is far easier/quicker for devs to test
their private code on their dev box.

[Simon Hayes]

In fact, I should have read a few more lines: "Installati ons of non-Web
serving applications are prohibited", which seems quite clear:

http://www.microsoft.com/windowsserv...rview/web.mspx

As for testing, that may be easy, but there's a risk that each
developer will modify his own environment in different ways (file
permissions, registry keys etc), and that creates problem for
integrating their code, deploying to standard production servers etc.

Simon

[rdhatt]

> In fact, I should have read a few more lines: "Installati ons of
non-Web

serving applications are prohibited", which seems quite clear: http://www.microsoft.com/windo*wsser...vi*ew/web.mspx
Right, but the MSDN license overrides it
(http://msdn.microsoft.com/subscripti...default.aspx):
"MSDN-licensed operating systems (OS) can be used as the primary OS as
long as the computer is used only for development and testing purposes"
Devs can't check their email on it, but they can develop on it.
As for testing, that may be easy, but there's a risk that each
developer will modify his own environment in different ways (file
permissions, registry keys etc), and that creates problem for
integrating their code, deploying to standard production servers etc.

Right, that's why we have our test cluster to shake out these
differences. We're trying to close the gap between those differences.
But we digress from my original question.

[Dan Guzman]

You might consider running Windows 2003 WE as a guest OS under Virtual PC.
This will allow devs to install the SQL tools on the host OS and use Windows
2003 WE virtual machine for testing under their MSDN license.

--
Hope this helps.

Dan Guzman
SQL Server MVP

<rd****@gmail.c om> wrote in message
news:11******** **************@ z14g2000cwz.goo glegroups.com.. .

Hi -

The developers in my company are all switching to Windows 2003 Web
Edition for their dev machines so they can better target the platform.
Unfortunately we have discovered that we unable to install the SQL
Server tools due (Query Analyzer, Profiler, etc) to the restriction
that SQL Server is not allowed. The devs run their databases on a
centeral server. Is there any workaround[1] to allow just the tools on
2003 WE?

Thanks!

[1] Installing another version of 2003 (Standard, Enterprise) is not an
good option since a) that isn't what our production servers run b) the
admin doesn't want to give the devs the ability to do something stupid,
like turn their desktop into a domain controller.

[Erland Sommarskog]

(rd****@gmail.c om) writes:

For the simple reason that it is far easier/quicker for devs to test
their private code on their dev box.

So run virtual machine (VMware or Virtual PC) with Web Edition, hosted
on the dev box. Or, run a virtual machine with XP hosted by the WE box.
This may not be licensed for Virtual PC (since this is an MS product),
but I would not really expect VMware to have any such restriction.

Or make the SQL tools available on another box, which the devs can access
with Remote Desktop.

Finally, I noted an announced for a query tool posted to this news
group. It's apparently more lightweight than QA, but maybe it's
sufficient for you. See
http://www.gmpservices.com/tabindex-...opDefault.aspx.
--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp