I'm doing some work for the clients who have SQL 2005 Small Business
versions.
I do not see Management Studio installed on their servers. On one of the
server I used a free version of Management Studio to attach database I
brought to install. Next time I needed to import data from another database
and it seems that Expess version doesn't support export/import.
I have a developer version of  SQL 2005 with installation CD.
My questions:
1. Is it possible technically to run setup of SQL 2005 again in order to add
Management Studio (from developer version CD) when an initial installation
was Small Business version of SQL?
2. If yes, then is it legal? Everything I need is to setup some databases
and then I don't need that tool on the client server. Microsoft allows to
run a trial version within 180 days. I need this tool for a fiew hours.
3. If not, then is there any way to buy only a full version of Management
Studio, or download a trial full version of Management Studio and use it for
a fiew hours for a real work?

Any other suggestions how to manage SQL 2005 Small Business edition please

Thank you

vovan

WHy not have the client pony up the $49 for their own copy of developer
edition?  That gives you full rights to use Management Studio on whatever
machine they install it...

Show quoteHide quote

Thank you.
English is not my language and I do not understand you.
Is it possible to buy a developer edition for $49? I got mine from MSDN
subscription, the price for it is much much higher.

vovan

Show quoteHide quote

Thanks again,
I just checked Microsoft site and found there SQL Developer edition for $49

Thank you very much.

vovan

Show quoteHide quote

Aaron Bertrand [SQL Server MVP] (ten.xoc@dnartreb.noraa) writes:
Does it? I mean, are the tools in Development Edition licensed for
production use?

As for the original post, I don't think the full-blown Mgmt Studio is
sufficient. You need Integration Services too to run export/import. Of
course, that is on the same 49$ CD, but it's still only licensed for
development.

I'm not sure, my lawyer's not here to go through the licensing agreement
with me.

Seems silly that it would be illegal, or that they could feasibly charge
more than $49 for the management tool for licenses of the engine, which cost
way more than that, and which are already paid for.  Don't production
licensed installations come with a CD that ships with the management tools?
(Of course they do.)  Are you really only licensed to manage the server from
the machine on which the engine is running, and can't pick another machine
to install the tools?  (I'm not sure, on that one.)  I guess it begs the
question, do they have the original CD from which they installed the
engine(s) on production machine(s)?  Surely they could install the
management tools from that CD instead of developer edition.  I was merely
suggesting a copy of developer edition as a *cheap* alternative to getting
the management tools for installation, should the original CDs be nowhere to
be found.  I wasn't talking about installing developer edition to run as a
production / fully licensed machine.

Not like an adherence audit could prove from which CD the tools came from,
anyway.  I think a lot of us (you excluded, I suppose) would be in trouble
if we had to log on to each physical server in order to manage production
servers... I manage my servers from my workstation, and if that's illegal,
then I guess someone's going to have to sick Microsoft on me, and/or teach
me how to manage many servers individually and still have time to sleep.
What edition of SQL Server are you running on your workstation?  Do you ever
use the tools installed there to manage or monitor production machines?

A

Aaron Bertrand [SQL Server MVP] (ten.xoc@dnartreb.noraa) writes:
Neither is mine. License issues are very difficult, I try to keep out as
much as I can. However, when someone suggests using Developer Edition to
manage a production system, I felt obliged to point out that this is may be
license breach, in case the person asking is anxious of not violating
licenses.

In general, to all people in these forums, who are asking questions about
SQL Server products, when it comes to licensing, you are best off to
contact your local Microsoft office, particularly if the question is
about some less common combination. I may know a lot of SQL Server, but
I can assure you that I never read a license agreement for SQL Server from
start to end. And, even if I did, I would not expect that it would help.

Hello Erland,

I would agree with your concern. Even though its logical to allow the use
of tools from developer edition to manage a production instance I don't think
you can.

However if you have a production instance you must have or be able to obtain
the media for said instance, which will have the tools on it.

I would expect one to be able to defend the use of developer edition but
its safer to go with what you have a licensed copy for.

Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons


Show quoteHide quote

And that's all I was really suggesting... if their production instance is
licensed, then surely one can defend using tools to manage it remotely...
regardless of where the tools came from.

I'd be really surprised to hear if any of us has a fully licensed
standard/enterprise engine on our workstations just so we can use *those*
tools to manage remote instances?  I notice Erland dodged that part of my
question.

Aaron Bertrand [SQL Server MVP] (ten.xoc@dnartreb.noraa) writes:
Apparently the engine here came with SBS, which probably has its own set
of license problems. And particularly, it appears that it does not come
with Mgmt Studio.

I gladly dodge anything about licenses.

Sorry, I missed that (first line of first post).

So, question for all, not directly for you, how are people who buy small
business server supposed to manage the SQL Server component of small
business server?

All right, maybe I'll corner you next week and we'll talk about it face to
face.  :-)

Aaron Bertrand [SQL Server MVP] (ten.xoc@dnartreb.noraa) writes:
Indeed a very interesting question!

Well, there is Mgmt Studio Express, but if SBS has Integration Services
and Agent, this is missing from SBS.

Then again, it seems that SBS comes with Workgroup Edition, so it should
have Mgmt Studio as well, but you never know...

I'm getting dizzy.  I haven't installed SBS so I'm not clear whether it
ships with Management Studio or not (you seem very unsure as well).  If it
does, then clearly, one should be able to install Management Studio to
manage it.  Otherwise, as you suggest, they would have to use Management
Studio Express or a third party tool.  I'm almost positive that Workgroup
Edition comes with Management Studio, so they should be okay...

As an aside, I have a dedicated server at a high-profile ISP, and it has
Workgroup Edition and they installed Management Studio -- not Express -- 
alongside.  It's not a guarantee, but I'm pretty sure they wouldn't risk
partner status etc. and violate license agreements just to provide me with a
tool I didn't even stipulate had to be installed locally...

A

I'm getting dizzy.  I haven't installed SBS so I'm not clear whether it
ships with Management Studio or not (you seem very unsure as well).  If it
does, then clearly, one should be able to install Management Studio to
manage it.  Otherwise, as you suggest, they would have to use Management
Studio Express or a third party tool.  I'm almost positive that Workgroup
Edition comes with Management Studio, so they should be okay...

As an aside, I have a dedicated server at a high-profile ISP, and it has
Workgroup Edition and they installed Management Studio -- not Express -- 
alongside.  It's not a guarantee, but I'm pretty sure they wouldn't risk
partner status etc. and violate license agreements just to provide me with a
tool I didn't even stipulate had to be installed locally...

A

The best move would be to use the copy of management studio that comes on
the Small Business Server CD's.  Here's an excerpt from the SBS setup
instructions:

On the Feature Selection page, click the icon next to SQL Server Database
Services, and then click Entire feature will be installed on local hard
drive. If it is not already expanded, expand Client Components. Click the
icon next to Management Tools, and then click Will be installed on local
hard drive. Ensure that Connectivity Tools are also selected for
installation. Click Next.



Show quoteHide quote

Hello Roger,

Are finally the voice of wisdom. This was starting to hurt my head.

Erland/Aaron
Remind me not to ask either of you anything about licensing next week.

Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons


Show quoteHide quote

What if the SBS CDs are not readily available (e.g. at the data center)?
Does it really matter which media I installed SSMS from, if I am licensed to
use it?

How many small businesses that you know of have a Data Center?  In my
experience all the CD's and DVD's are in the same drawer.  If you followed
the instructions when you did the original install, SSMS would be there from
the beginning.

Show quoteHide quote

Come on Roger, just because a company has a data center does not mean that
all of their SQL Server instances are Enterprise Edition.  SBS offers a lot
of things that a company with money can do, that they can't do with just SQL
Server by itself out of the box, at least not very quickly.

Sorry, I missed that (first line of first post).

So, question for all, not directly for you, how are people who buy small
business server supposed to manage the SQL Server component of small
business server?

All right, maybe I'll corner you next week and we'll talk about it face to
face.  :-)

On Mar 2, 5:48 pm, Erland Sommarskog <esq***@sommarskog.se> wrote:
Show quoteHide quoteYes it is only meant for development.

How can I print my SQL Server agent jobs?
Query to split Firstname Lastname into 2 fields
Profiler: SQL:StmtRecompile - EvenSubClass definitions?
sp_trace_setfilter does not work
Error passing accented characters to Oracle