Check this out
this is the replacement for MSDE 2000
SQL Server 2005 Express Edition (http://lab.msdn.microsoft.com/express/sql/default.aspx)
Top 10 cool things about SQL Server Express Edition (http://lab.msdn.microsoft.com/express/sql/top10/default.aspx)
SQL Server Express Books Online (http://www.microsoft.com/downloads/details.aspx?FamilyId=2ADBC1A8-AE5C-497D-B584-EAB6719300CD&displaylang=en)
by the way if you follow the first link, you will find a pretty accurate photo of rdjabarov...Check this out
you will find a pretty accurate photo of rdjabarov...
Looks pretty nice and decent just like the Express Edition. Where he's from by the way, USA!!|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?|||Hey now, I'm from Ala-freaking-bama|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?
i'm just kidding
but on further reflection he kind of looks like fabian pascal.
Pat can verify that for us because as we all know, he's fabian's best friend.|||Do you really believe that I think that way?..Well, I DO love Texas, but I am ready for a change (ideally would be to move without my kids knowing where to :D )|||Anyone else think that CLR is a bunch of nonsense?|||Anyone else think that CLR is a bunch of nonsense?
I think it's VERY neat. I also think that this will force some hard core production DBA's to have a hard look at themselves and see if the career they've chosen is what they want to continue pursuing. Personally, I am happy with a definition that is given to me, - hybrid DBA! And the direction the job description is taking is where I am at now.|||Pat can verify that for us because as we all know, he's fabian's best friend.It's good to be loved, isn't it? Actually, I've never met Fabian in person, or even seen a picture from a reliable source, so I'm no authority there. It's hard to imagine that I've never seen anyone that loves me so, isn't it?
-PatP|||Anyone else think that CLR is a bunch of nonsense?Not really, I think that the CLR brings a lot of interesting benefits, but it brings some new risks in the baggage with it.
The benefits are basically the ones that UCSD promised with the p-machine and Java didn't quite deliver with their virtual machine. A standard, more or less hardware independant virtual machine. One code base for many platforms. One target for many compilers, which allows much better tools to evolve because the economies of scale kick in much sooner.
The big risks seem to be that once something makes it into the runtime, who will ensure that it makes sense for it to stay there as it evolves. Many things that make perfect sense on the desktop (or even handheld) are a positive liability on a server!
It is a two edged sword. It brings many benefits, but at a significant cost.
-PatP|||I think it's VERY neat.
Why? And yes, PROD DBA's who sit there waiting for an alert...sure...but someones got to do that...and I'm glad it's not me...not sure if they even know what a sproc is...let alone a trigger...
And what can you do with "External Procedures" (CLR) that you can't do with T-SQL or it's extensions?
CLR is just more overhead...
And I'd love to see what they mean by Extensive XML support...
What? Did they add Relational extenders to XML?|||Well, I've run to the rescue of "External Procedures" via sp_oaxxx. You're write, the same thing can be accomplished by T-SQL, but the final choice is based on many factors. I prefer to use a tool for a task that is designed to do that task. Of course I can create a file using T-SQL, but if there is a better way to do the same thing (Scripting.FileSystemObject) I'd pick that one.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)|||I think Pat summed it up pretty well. There are some things that the CLR will just do better. There's also a LOT of risk if it's used wrong. The XML thing actually worries me more then the CLR though. It's harking back to the days of hierarchial design and promising "extensibility". I have a feeling we'll end up regretting the degradation of a relational environment to cater to the desires of a shortcut "extend into anything without considering the consequences" world. Oh well....rant off.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)
Right on, man, right on!
Showing posts with label lab. Show all posts
Showing posts with label lab. Show all posts
Friday, March 23, 2012
Friday, March 9, 2012
New Instance
I'd like to install a named instance of SQL server, if this is just for
testing in the dev lab do I still need to have a license for it?
In the prod version I have one instance with several databases can I give
another DBA rights to view and admin only one database of that list. How do
I restrict the other DBA from viewing other databases?
ThanksHi
This seems to be something I am never 100% sure about, so it would be better
to clarify it with you software provider. I think the answer depends on how
you have licenced your current copy and what version it is:
For Server + User Cal licencing
http://www.microsoft.com/sql/howtobuy/serverpluscal.asp
1. GRANT OF LICENSE. Microsoft grants you the following rights, provided you
comply with all terms and conditions of this EULA:
a. Installation-Server Software. You may install and use one copy of the
Server Software on a single Server. SQL Server Enterprise Edition. If
you have acquired the Enterprise Edition of the Server Software, you may
install any number of instances of the Server Software on
that Server. An "instance" shall mean a running copy of the Server Software.
Client Software. You may install the Client Software (SQL
Server Personal Edition) on any internal Device.
Server + Device cals seems to be similar to User Cal
http://www.microsoft.com/sql/howtobuy/servercal.asp
For processor licencing http://www.microsoft.com/sql/howtobuy/processor.asp:
1. GRANT OF LICENSE. Microsoft grants you the following rights, provided you
comply with all terms and conditions of this EULA:
a. License Structure. The Server Software is licensed on an individual
processor basis. You need one Server Software license for each of
your Server's processors. As an exception to that rule, if you have made a
processor inaccessible to all operating system copies on
which the Server Software is set up to run, you do not need a Server
Software license for that processor. Examples of processors that
you have made inaccessible to operating system copies are processors that
you have isolated by partitioning or other similar method.
You do not need more than one Server Software license for any processor.
b. Server Software. You may install and run any number of copies of the
Server Software on a single Server. You may use the
Management Tools, Books-Online, and Development Tools components of
Microsoft SQL Server (collectively "Tools") solely for
internal use in conjunction with your Server Software.
This would imply you can have multiple instances.
HTH
John
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:E2B9F076-111F-40F6-95CC-6266A19907C5@.microsoft.com...
> I'd like to install a named instance of SQL server, if this is just for
> testing in the dev lab do I still need to have a license for it?
> In the prod version I have one instance with several databases can I give
> another DBA rights to view and admin only one database of that list. How
> do
> I restrict the other DBA from viewing other databases?
> Thanks|||Niles wrote:
> I'd like to install a named instance of SQL server, if this is just
> for testing in the dev lab do I still need to have a license for it?
> In the prod version I have one instance with several databases can I
> give another DBA rights to view and admin only one database of that
> list. How do I restrict the other DBA from viewing other databases?
> Thanks
They can still "see" the other database names, but you can assign them
access to only the database they are supposed to maintain.
--
David Gugick
Imceda Software
www.imceda.com|||Per Server Licensing, you need additional Server License.
Per CPU, no additional licensing is required as long as you are properly
licenses for each CPU in the machine.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ONsggru4EHA.1300@.TK2MSFTNGP14.phx.gbl...
> Hi
> This seems to be something I am never 100% sure about, so it would be
better
> to clarify it with you software provider. I think the answer depends on
how
> you have licenced your current copy and what version it is:
> For Server + User Cal licencing
> http://www.microsoft.com/sql/howtobuy/serverpluscal.asp
> 1. GRANT OF LICENSE. Microsoft grants you the following rights, provided
you
> comply with all terms and conditions of this EULA:
> a. Installation-Server Software. You may install and use one copy of the
> Server Software on a single Server. SQL Server Enterprise Edition. If
> you have acquired the Enterprise Edition of the Server Software, you may
> install any number of instances of the Server Software on
> that Server. An "instance" shall mean a running copy of the Server
Software.
> Client Software. You may install the Client Software (SQL
> Server Personal Edition) on any internal Device.
> Server + Device cals seems to be similar to User Cal
> http://www.microsoft.com/sql/howtobuy/servercal.asp
> For processor licencing
http://www.microsoft.com/sql/howtobuy/processor.asp:
> 1. GRANT OF LICENSE. Microsoft grants you the following rights, provided
you
> comply with all terms and conditions of this EULA:
> a. License Structure. The Server Software is licensed on an individual
> processor basis. You need one Server Software license for each of
> your Server's processors. As an exception to that rule, if you have made a
> processor inaccessible to all operating system copies on
> which the Server Software is set up to run, you do not need a Server
> Software license for that processor. Examples of processors that
> you have made inaccessible to operating system copies are processors that
> you have isolated by partitioning or other similar method.
> You do not need more than one Server Software license for any processor.
> b. Server Software. You may install and run any number of copies of the
> Server Software on a single Server. You may use the
> Management Tools, Books-Online, and Development Tools components of
> Microsoft SQL Server (collectively "Tools") solely for
> internal use in conjunction with your Server Software.
> This would imply you can have multiple instances.
> HTH
> John
>
> "Niles" <Niles@.discussions.microsoft.com> wrote in message
> news:E2B9F076-111F-40F6-95CC-6266A19907C5@.microsoft.com...
> > I'd like to install a named instance of SQL server, if this is just for
> > testing in the dev lab do I still need to have a license for it?
> >
> > In the prod version I have one instance with several databases can I
give
> > another DBA rights to view and admin only one database of that list.
How
> > do
> > I restrict the other DBA from viewing other databases?
> >
> > Thanks
>|||I haven't tested this yet but If I put a database under a named instance can
I then give them access to that instance only?
Thanks
"David Gugick" wrote:
> Niles wrote:
> > I'd like to install a named instance of SQL server, if this is just
> > for testing in the dev lab do I still need to have a license for it?
> >
> > In the prod version I have one instance with several databases can I
> > give another DBA rights to view and admin only one database of that
> > list. How do I restrict the other DBA from viewing other databases?
> >
> > Thanks
> They can still "see" the other database names, but you can assign them
> access to only the database they are supposed to maintain.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
testing in the dev lab do I still need to have a license for it?
In the prod version I have one instance with several databases can I give
another DBA rights to view and admin only one database of that list. How do
I restrict the other DBA from viewing other databases?
ThanksHi
This seems to be something I am never 100% sure about, so it would be better
to clarify it with you software provider. I think the answer depends on how
you have licenced your current copy and what version it is:
For Server + User Cal licencing
http://www.microsoft.com/sql/howtobuy/serverpluscal.asp
1. GRANT OF LICENSE. Microsoft grants you the following rights, provided you
comply with all terms and conditions of this EULA:
a. Installation-Server Software. You may install and use one copy of the
Server Software on a single Server. SQL Server Enterprise Edition. If
you have acquired the Enterprise Edition of the Server Software, you may
install any number of instances of the Server Software on
that Server. An "instance" shall mean a running copy of the Server Software.
Client Software. You may install the Client Software (SQL
Server Personal Edition) on any internal Device.
Server + Device cals seems to be similar to User Cal
http://www.microsoft.com/sql/howtobuy/servercal.asp
For processor licencing http://www.microsoft.com/sql/howtobuy/processor.asp:
1. GRANT OF LICENSE. Microsoft grants you the following rights, provided you
comply with all terms and conditions of this EULA:
a. License Structure. The Server Software is licensed on an individual
processor basis. You need one Server Software license for each of
your Server's processors. As an exception to that rule, if you have made a
processor inaccessible to all operating system copies on
which the Server Software is set up to run, you do not need a Server
Software license for that processor. Examples of processors that
you have made inaccessible to operating system copies are processors that
you have isolated by partitioning or other similar method.
You do not need more than one Server Software license for any processor.
b. Server Software. You may install and run any number of copies of the
Server Software on a single Server. You may use the
Management Tools, Books-Online, and Development Tools components of
Microsoft SQL Server (collectively "Tools") solely for
internal use in conjunction with your Server Software.
This would imply you can have multiple instances.
HTH
John
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:E2B9F076-111F-40F6-95CC-6266A19907C5@.microsoft.com...
> I'd like to install a named instance of SQL server, if this is just for
> testing in the dev lab do I still need to have a license for it?
> In the prod version I have one instance with several databases can I give
> another DBA rights to view and admin only one database of that list. How
> do
> I restrict the other DBA from viewing other databases?
> Thanks|||Niles wrote:
> I'd like to install a named instance of SQL server, if this is just
> for testing in the dev lab do I still need to have a license for it?
> In the prod version I have one instance with several databases can I
> give another DBA rights to view and admin only one database of that
> list. How do I restrict the other DBA from viewing other databases?
> Thanks
They can still "see" the other database names, but you can assign them
access to only the database they are supposed to maintain.
--
David Gugick
Imceda Software
www.imceda.com|||Per Server Licensing, you need additional Server License.
Per CPU, no additional licensing is required as long as you are properly
licenses for each CPU in the machine.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ONsggru4EHA.1300@.TK2MSFTNGP14.phx.gbl...
> Hi
> This seems to be something I am never 100% sure about, so it would be
better
> to clarify it with you software provider. I think the answer depends on
how
> you have licenced your current copy and what version it is:
> For Server + User Cal licencing
> http://www.microsoft.com/sql/howtobuy/serverpluscal.asp
> 1. GRANT OF LICENSE. Microsoft grants you the following rights, provided
you
> comply with all terms and conditions of this EULA:
> a. Installation-Server Software. You may install and use one copy of the
> Server Software on a single Server. SQL Server Enterprise Edition. If
> you have acquired the Enterprise Edition of the Server Software, you may
> install any number of instances of the Server Software on
> that Server. An "instance" shall mean a running copy of the Server
Software.
> Client Software. You may install the Client Software (SQL
> Server Personal Edition) on any internal Device.
> Server + Device cals seems to be similar to User Cal
> http://www.microsoft.com/sql/howtobuy/servercal.asp
> For processor licencing
http://www.microsoft.com/sql/howtobuy/processor.asp:
> 1. GRANT OF LICENSE. Microsoft grants you the following rights, provided
you
> comply with all terms and conditions of this EULA:
> a. License Structure. The Server Software is licensed on an individual
> processor basis. You need one Server Software license for each of
> your Server's processors. As an exception to that rule, if you have made a
> processor inaccessible to all operating system copies on
> which the Server Software is set up to run, you do not need a Server
> Software license for that processor. Examples of processors that
> you have made inaccessible to operating system copies are processors that
> you have isolated by partitioning or other similar method.
> You do not need more than one Server Software license for any processor.
> b. Server Software. You may install and run any number of copies of the
> Server Software on a single Server. You may use the
> Management Tools, Books-Online, and Development Tools components of
> Microsoft SQL Server (collectively "Tools") solely for
> internal use in conjunction with your Server Software.
> This would imply you can have multiple instances.
> HTH
> John
>
> "Niles" <Niles@.discussions.microsoft.com> wrote in message
> news:E2B9F076-111F-40F6-95CC-6266A19907C5@.microsoft.com...
> > I'd like to install a named instance of SQL server, if this is just for
> > testing in the dev lab do I still need to have a license for it?
> >
> > In the prod version I have one instance with several databases can I
give
> > another DBA rights to view and admin only one database of that list.
How
> > do
> > I restrict the other DBA from viewing other databases?
> >
> > Thanks
>|||I haven't tested this yet but If I put a database under a named instance can
I then give them access to that instance only?
Thanks
"David Gugick" wrote:
> Niles wrote:
> > I'd like to install a named instance of SQL server, if this is just
> > for testing in the dev lab do I still need to have a license for it?
> >
> > In the prod version I have one instance with several databases can I
> > give another DBA rights to view and admin only one database of that
> > list. How do I restrict the other DBA from viewing other databases?
> >
> > Thanks
> They can still "see" the other database names, but you can assign them
> access to only the database they are supposed to maintain.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
New Instance
I'd like to install a named instance of SQL server, if this is just for
testing in the dev lab do I still need to have a license for it?
In the prod version I have one instance with several databases can I give
another DBA rights to view and admin only one database of that list. How do
I restrict the other DBA from viewing other databases?
Thanks
Hi
This seems to be something I am never 100% sure about, so it would be better
to clarify it with you software provider. I think the answer depends on how
you have licenced your current copy and what version it is:
For Server + User Cal licencing
http://www.microsoft.com/sql/howtobuy/serverpluscal.asp
1. GRANT OF LICENSE. Microsoft grants you the following rights, provided you
comply with all terms and conditions of this EULA:
a. Installation-Server Software. You may install and use one copy of the
Server Software on a single Server. SQL Server Enterprise Edition. If
you have acquired the Enterprise Edition of the Server Software, you may
install any number of instances of the Server Software on
that Server. An "instance" shall mean a running copy of the Server Software.
Client Software. You may install the Client Software (SQL
Server Personal Edition) on any internal Device.
Server + Device cals seems to be similar to User Cal
http://www.microsoft.com/sql/howtobuy/servercal.asp
For processor licencing http://www.microsoft.com/sql/howtobuy/processor.asp:
1. GRANT OF LICENSE. Microsoft grants you the following rights, provided you
comply with all terms and conditions of this EULA:
a. License Structure. The Server Software is licensed on an individual
processor basis. You need one Server Software license for each of
your Server's processors. As an exception to that rule, if you have made a
processor inaccessible to all operating system copies on
which the Server Software is set up to run, you do not need a Server
Software license for that processor. Examples of processors that
you have made inaccessible to operating system copies are processors that
you have isolated by partitioning or other similar method.
You do not need more than one Server Software license for any processor.
b. Server Software. You may install and run any number of copies of the
Server Software on a single Server. You may use the
Management Tools, Books-Online, and Development Tools components of
Microsoft SQL Server (collectively "Tools") solely for
internal use in conjunction with your Server Software.
This would imply you can have multiple instances.
HTH
John
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:E2B9F076-111F-40F6-95CC-6266A19907C5@.microsoft.com...
> I'd like to install a named instance of SQL server, if this is just for
> testing in the dev lab do I still need to have a license for it?
> In the prod version I have one instance with several databases can I give
> another DBA rights to view and admin only one database of that list. How
> do
> I restrict the other DBA from viewing other databases?
> Thanks
|||Niles wrote:
> I'd like to install a named instance of SQL server, if this is just
> for testing in the dev lab do I still need to have a license for it?
> In the prod version I have one instance with several databases can I
> give another DBA rights to view and admin only one database of that
> list. How do I restrict the other DBA from viewing other databases?
> Thanks
They can still "see" the other database names, but you can assign them
access to only the database they are supposed to maintain.
David Gugick
Imceda Software
www.imceda.com
|||Per Server Licensing, you need additional Server License.
Per CPU, no additional licensing is required as long as you are properly
licenses for each CPU in the machine.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ONsggru4EHA.1300@.TK2MSFTNGP14.phx.gbl...
> Hi
> This seems to be something I am never 100% sure about, so it would be
better
> to clarify it with you software provider. I think the answer depends on
how
> you have licenced your current copy and what version it is:
> For Server + User Cal licencing
> http://www.microsoft.com/sql/howtobuy/serverpluscal.asp
> 1. GRANT OF LICENSE. Microsoft grants you the following rights, provided
you
> comply with all terms and conditions of this EULA:
> a. Installation-Server Software. You may install and use one copy of the
> Server Software on a single Server. SQL Server Enterprise Edition. If
> you have acquired the Enterprise Edition of the Server Software, you may
> install any number of instances of the Server Software on
> that Server. An "instance" shall mean a running copy of the Server
Software.
> Client Software. You may install the Client Software (SQL
> Server Personal Edition) on any internal Device.
> Server + Device cals seems to be similar to User Cal
> http://www.microsoft.com/sql/howtobuy/servercal.asp
> For processor licencing
http://www.microsoft.com/sql/howtobuy/processor.asp:
> 1. GRANT OF LICENSE. Microsoft grants you the following rights, provided
you[vbcol=seagreen]
> comply with all terms and conditions of this EULA:
> a. License Structure. The Server Software is licensed on an individual
> processor basis. You need one Server Software license for each of
> your Server's processors. As an exception to that rule, if you have made a
> processor inaccessible to all operating system copies on
> which the Server Software is set up to run, you do not need a Server
> Software license for that processor. Examples of processors that
> you have made inaccessible to operating system copies are processors that
> you have isolated by partitioning or other similar method.
> You do not need more than one Server Software license for any processor.
> b. Server Software. You may install and run any number of copies of the
> Server Software on a single Server. You may use the
> Management Tools, Books-Online, and Development Tools components of
> Microsoft SQL Server (collectively "Tools") solely for
> internal use in conjunction with your Server Software.
> This would imply you can have multiple instances.
> HTH
> John
>
> "Niles" <Niles@.discussions.microsoft.com> wrote in message
> news:E2B9F076-111F-40F6-95CC-6266A19907C5@.microsoft.com...
give[vbcol=seagreen]
How
>
|||I haven't tested this yet but If I put a database under a named instance can
I then give them access to that instance only?
Thanks
"David Gugick" wrote:
> Niles wrote:
> They can still "see" the other database names, but you can assign them
> access to only the database they are supposed to maintain.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
testing in the dev lab do I still need to have a license for it?
In the prod version I have one instance with several databases can I give
another DBA rights to view and admin only one database of that list. How do
I restrict the other DBA from viewing other databases?
Thanks
Hi
This seems to be something I am never 100% sure about, so it would be better
to clarify it with you software provider. I think the answer depends on how
you have licenced your current copy and what version it is:
For Server + User Cal licencing
http://www.microsoft.com/sql/howtobuy/serverpluscal.asp
1. GRANT OF LICENSE. Microsoft grants you the following rights, provided you
comply with all terms and conditions of this EULA:
a. Installation-Server Software. You may install and use one copy of the
Server Software on a single Server. SQL Server Enterprise Edition. If
you have acquired the Enterprise Edition of the Server Software, you may
install any number of instances of the Server Software on
that Server. An "instance" shall mean a running copy of the Server Software.
Client Software. You may install the Client Software (SQL
Server Personal Edition) on any internal Device.
Server + Device cals seems to be similar to User Cal
http://www.microsoft.com/sql/howtobuy/servercal.asp
For processor licencing http://www.microsoft.com/sql/howtobuy/processor.asp:
1. GRANT OF LICENSE. Microsoft grants you the following rights, provided you
comply with all terms and conditions of this EULA:
a. License Structure. The Server Software is licensed on an individual
processor basis. You need one Server Software license for each of
your Server's processors. As an exception to that rule, if you have made a
processor inaccessible to all operating system copies on
which the Server Software is set up to run, you do not need a Server
Software license for that processor. Examples of processors that
you have made inaccessible to operating system copies are processors that
you have isolated by partitioning or other similar method.
You do not need more than one Server Software license for any processor.
b. Server Software. You may install and run any number of copies of the
Server Software on a single Server. You may use the
Management Tools, Books-Online, and Development Tools components of
Microsoft SQL Server (collectively "Tools") solely for
internal use in conjunction with your Server Software.
This would imply you can have multiple instances.
HTH
John
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:E2B9F076-111F-40F6-95CC-6266A19907C5@.microsoft.com...
> I'd like to install a named instance of SQL server, if this is just for
> testing in the dev lab do I still need to have a license for it?
> In the prod version I have one instance with several databases can I give
> another DBA rights to view and admin only one database of that list. How
> do
> I restrict the other DBA from viewing other databases?
> Thanks
|||Niles wrote:
> I'd like to install a named instance of SQL server, if this is just
> for testing in the dev lab do I still need to have a license for it?
> In the prod version I have one instance with several databases can I
> give another DBA rights to view and admin only one database of that
> list. How do I restrict the other DBA from viewing other databases?
> Thanks
They can still "see" the other database names, but you can assign them
access to only the database they are supposed to maintain.
David Gugick
Imceda Software
www.imceda.com
|||Per Server Licensing, you need additional Server License.
Per CPU, no additional licensing is required as long as you are properly
licenses for each CPU in the machine.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ONsggru4EHA.1300@.TK2MSFTNGP14.phx.gbl...
> Hi
> This seems to be something I am never 100% sure about, so it would be
better
> to clarify it with you software provider. I think the answer depends on
how
> you have licenced your current copy and what version it is:
> For Server + User Cal licencing
> http://www.microsoft.com/sql/howtobuy/serverpluscal.asp
> 1. GRANT OF LICENSE. Microsoft grants you the following rights, provided
you
> comply with all terms and conditions of this EULA:
> a. Installation-Server Software. You may install and use one copy of the
> Server Software on a single Server. SQL Server Enterprise Edition. If
> you have acquired the Enterprise Edition of the Server Software, you may
> install any number of instances of the Server Software on
> that Server. An "instance" shall mean a running copy of the Server
Software.
> Client Software. You may install the Client Software (SQL
> Server Personal Edition) on any internal Device.
> Server + Device cals seems to be similar to User Cal
> http://www.microsoft.com/sql/howtobuy/servercal.asp
> For processor licencing
http://www.microsoft.com/sql/howtobuy/processor.asp:
> 1. GRANT OF LICENSE. Microsoft grants you the following rights, provided
you[vbcol=seagreen]
> comply with all terms and conditions of this EULA:
> a. License Structure. The Server Software is licensed on an individual
> processor basis. You need one Server Software license for each of
> your Server's processors. As an exception to that rule, if you have made a
> processor inaccessible to all operating system copies on
> which the Server Software is set up to run, you do not need a Server
> Software license for that processor. Examples of processors that
> you have made inaccessible to operating system copies are processors that
> you have isolated by partitioning or other similar method.
> You do not need more than one Server Software license for any processor.
> b. Server Software. You may install and run any number of copies of the
> Server Software on a single Server. You may use the
> Management Tools, Books-Online, and Development Tools components of
> Microsoft SQL Server (collectively "Tools") solely for
> internal use in conjunction with your Server Software.
> This would imply you can have multiple instances.
> HTH
> John
>
> "Niles" <Niles@.discussions.microsoft.com> wrote in message
> news:E2B9F076-111F-40F6-95CC-6266A19907C5@.microsoft.com...
give[vbcol=seagreen]
How
>
|||I haven't tested this yet but If I put a database under a named instance can
I then give them access to that instance only?
Thanks
"David Gugick" wrote:
> Niles wrote:
> They can still "see" the other database names, but you can assign them
> access to only the database they are supposed to maintain.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
Subscribe to:
Posts (Atom)