I have three questions: Could anyone help.
1. How much does a Microsoft SQL Server client license cost?
2. If we have web interface as the front end and SQL server as the back end,
do we need client licenses for those accessing their databases via the web?
3. Also if we have people accessing the server with Access,do we need
licenses for those?
"bgm" <bgm@.discussions.microsoft.com> wrote in message
news:17913AFE-A04D-47B3-96A7-C4216A68E6D8@.microsoft.com...
> I have three questions: Could anyone help.
> 1. How much does a Microsoft SQL Server client license cost?
http://www.microsoft.com/sql/howtobuy/default.asp
> 2. If we have web interface as the front end and SQL server as the back
end,
> do we need client licenses for those accessing their databases via the
web?
It's better to buy a per-processor licence because you do not know the
number of users (or you have developed a database access componenet and you
need to limit the number of concurrent users).
> 3. Also if we have people accessing the server with Access,do we need
> licenses for those?
It's an extra connection.
|||>> 2. If we have web interface as the front end and SQL server as the back
> end,
> web?
> It's better to buy a per-processor licence because you do not know the
> number of users (or you have developed a database access componenet and
> you
> need to limit the number of concurrent users).
the only option is per processor license! You can't use per user connection
license.
Friday, March 30, 2012
Microsoft SQL Server client license costs
I have three questions here:Could anyone help.
1.How much does a Microsoft SQL Server client license cost?
2.If we have web interface as the front end and SQL server as the back
end,do we need client licenses for those accessing the databases via the web?
3.If we have people accessing the server with Access,do we need licenses for
those?
Hi,
You can check the following whitepaper and article for information on SQL
Server licensing and prices
http://www.microsoft.com/sql/howtobu...licensing.asp.
http://www.microsoft.com/sql/howtobuy/faq.asp
You can also call (800) 426-9400 to clarify your doubts on the licensing.
Regards,
Gayathri Rau [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
1.How much does a Microsoft SQL Server client license cost?
2.If we have web interface as the front end and SQL server as the back
end,do we need client licenses for those accessing the databases via the web?
3.If we have people accessing the server with Access,do we need licenses for
those?
Hi,
You can check the following whitepaper and article for information on SQL
Server licensing and prices
http://www.microsoft.com/sql/howtobu...licensing.asp.
http://www.microsoft.com/sql/howtobuy/faq.asp
You can also call (800) 426-9400 to clarify your doubts on the licensing.
Regards,
Gayathri Rau [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
Microsoft SQL Server Certifications
Hello all,
I'm working as DBA.I wish to do certifications for Microsoft sql server.So Could i know what are the certifications are available and what i've to do for certififcations.
Thanks in advance
David RPlease find all the details here.
Microsoft SQL Server Best Practices Analyzer
Should this tool be installed and run in a production server?
MM
barney@.newsgroups.nospam
Martin,
If you are concerned about installing this tool on production server, you
can install this tool on a remote machine and you could analyze a production
server from a remote machine (as long as you can connect to target SQL
Server from remote machine)
SQL Best Practices Analyzer relies on the BPA Repository database, which is
a SQL Server database created during SQL BPA installation. You can have this
BPA repository database created on local SQL Server or a remote SQL Server.
SQL Best Practices Analyzer requires the following components to be
installed on the machine
.. Microsoft Internet Explorer 6.0 or later
.. Microsoft .Net Framework 1.1
Reference:
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Sethu
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
"Martin Millar" <barney@.newsgroups.nospam> wrote in message
news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
> Should this tool be installed and run in a production server?
> --
> MM
> barney@.newsgroups.nospam
|||Thanks for this. perhaps I should have been a bit more precise. I am a
developer and I'm having a beef with my DBA who has installed this on the
live production server. My argument is that this should be installed and run
on a test system as there is no need to test the performance of the hardware
on which the DB runs on.
If it's OK on Test then it gets ported to live. I believe that anything that
does not need to be installed on a production server should not be on there
as there is a danger that something else running on the box may result in a
loss of service or may intoduce a risk of virus or attack. This tool requires
the dot.net framework and I am a strong fan of this being an asp.net
developer. But until this (dot.net) becomes a core part of the OS (i.e. when
it's installed by default on XP, win2003 etc) I categorise this as a
development add-on and has an attached if installed.
If MS release a security patch for dot.net then I need to schedule downtime
on the production server to apply this.
So back to my original question, which is in itself is about best practises,
should it be best practise to install the BPA on a production server?
Thanks in advance
"Sethu Srinivasan [MSFT]" wrote:
> Martin,
> If you are concerned about installing this tool on production server, you
> can install this tool on a remote machine and you could analyze a production
> server from a remote machine (as long as you can connect to target SQL
> Server from remote machine)
> SQL Best Practices Analyzer relies on the BPA Repository database, which is
> a SQL Server database created during SQL BPA installation. You can have this
> BPA repository database created on local SQL Server or a remote SQL Server.
> SQL Best Practices Analyzer requires the following components to be
> installed on the machine
> .. Microsoft Internet Explorer 6.0 or later
> .. Microsoft .Net Framework 1.1
> Reference:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Thanks
> Sethu
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm.
>
> "Martin Millar" <barney@.newsgroups.nospam> wrote in message
> news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
>
>
MM
barney@.newsgroups.nospam
Martin,
If you are concerned about installing this tool on production server, you
can install this tool on a remote machine and you could analyze a production
server from a remote machine (as long as you can connect to target SQL
Server from remote machine)
SQL Best Practices Analyzer relies on the BPA Repository database, which is
a SQL Server database created during SQL BPA installation. You can have this
BPA repository database created on local SQL Server or a remote SQL Server.
SQL Best Practices Analyzer requires the following components to be
installed on the machine
.. Microsoft Internet Explorer 6.0 or later
.. Microsoft .Net Framework 1.1
Reference:
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Sethu
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
"Martin Millar" <barney@.newsgroups.nospam> wrote in message
news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
> Should this tool be installed and run in a production server?
> --
> MM
> barney@.newsgroups.nospam
|||Thanks for this. perhaps I should have been a bit more precise. I am a
developer and I'm having a beef with my DBA who has installed this on the
live production server. My argument is that this should be installed and run
on a test system as there is no need to test the performance of the hardware
on which the DB runs on.
If it's OK on Test then it gets ported to live. I believe that anything that
does not need to be installed on a production server should not be on there
as there is a danger that something else running on the box may result in a
loss of service or may intoduce a risk of virus or attack. This tool requires
the dot.net framework and I am a strong fan of this being an asp.net
developer. But until this (dot.net) becomes a core part of the OS (i.e. when
it's installed by default on XP, win2003 etc) I categorise this as a
development add-on and has an attached if installed.
If MS release a security patch for dot.net then I need to schedule downtime
on the production server to apply this.
So back to my original question, which is in itself is about best practises,
should it be best practise to install the BPA on a production server?
Thanks in advance
"Sethu Srinivasan [MSFT]" wrote:
> Martin,
> If you are concerned about installing this tool on production server, you
> can install this tool on a remote machine and you could analyze a production
> server from a remote machine (as long as you can connect to target SQL
> Server from remote machine)
> SQL Best Practices Analyzer relies on the BPA Repository database, which is
> a SQL Server database created during SQL BPA installation. You can have this
> BPA repository database created on local SQL Server or a remote SQL Server.
> SQL Best Practices Analyzer requires the following components to be
> installed on the machine
> .. Microsoft Internet Explorer 6.0 or later
> .. Microsoft .Net Framework 1.1
> Reference:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Thanks
> Sethu
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm.
>
> "Martin Millar" <barney@.newsgroups.nospam> wrote in message
> news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
>
>
Microsoft SQL Server and Other DBMS
Hello:
Many companies use DBMS that are not Microsoft SQL Server. Those companies use Oracle, PostgreSQL, MySQL and Ingres, for example. I'm looking for a paper o website which exponses the advantages (strengths) and disadvantages (weakness) of those DBMS. Why? Our customers would like a comparison between different systems, and we must show them the Microsoft SQL Server possibilities.
Can you help me with this? In terms of performance, speed, security, maintenance, etc.
Thanks.
We offer comparison information for SQL Server at http://www.microsoft.com/sql/prodinfo/compare/default.mspx, this information should help you start filling out the information you need to compare the different RDBMS systems out there.
Mike
Microsoft SQL Server and Other DBMS
Hello:
Many companies use DBMS that are not Microsoft SQL Server. Those companies use Oracle, PostgreSQL, MySQL and Ingres, for example. I'm looking for a paper o website which exponses the advantages (strengths) and disadvantages (weakness) of those DBMS. Why? Our customers would like a comparison between different systems, and we must show them the Microsoft SQL Server possibilities.
Can you help me with this? In terms of performance, speed, security, maintenance, etc.
Thanks.
We offer comparison information for SQL Server at http://www.microsoft.com/sql/prodinfo/compare/default.mspx, this information should help you start filling out the information you need to compare the different RDBMS systems out there.
Mike
Microsoft SQL server 6.5 to 2005
Hi Fellas,
I would really appreciate if you could help me out with the following two questions?
1) Can 2005 server files be converted to 6.5? and how?
2) How easy it to upgrade from 6.5 to 2005? and how?
I would be really grateful by your help
NickNot so easy task to do as you have to compare each and every aspect of the database to ensure they work in compatibility of SQL 2005.
Refer to http://sqlserver-qa.net/blogs/tools/archive/2007/04/12/set-a-stage-for-smooth-upgrades-of-your-sql-server-environment.aspx & http://sqlserver-qa.net/blogs/tools/pages/easy-way-to-upgrade-from-previous-version-of-sql-server.aspx in this case.|||Thanks a lot, i appreciate.|||Maverick
I should imagine it would depend on the size & complexity of the 6.5 DB
For a simple DB I would probably just script out the Schema then, run script & right click - import the data on the 2005 box then - suck it & see fixing any issues (IF there are any) in testing.
Or you could spend your life reading up on the possible failures & effects that may occur as Satya suggests
GWsql
I would really appreciate if you could help me out with the following two questions?
1) Can 2005 server files be converted to 6.5? and how?
2) How easy it to upgrade from 6.5 to 2005? and how?
I would be really grateful by your help
NickNot so easy task to do as you have to compare each and every aspect of the database to ensure they work in compatibility of SQL 2005.
Refer to http://sqlserver-qa.net/blogs/tools/archive/2007/04/12/set-a-stage-for-smooth-upgrades-of-your-sql-server-environment.aspx & http://sqlserver-qa.net/blogs/tools/pages/easy-way-to-upgrade-from-previous-version-of-sql-server.aspx in this case.|||Thanks a lot, i appreciate.|||Maverick
I should imagine it would depend on the size & complexity of the 6.5 DB
For a simple DB I would probably just script out the Schema then, run script & right click - import the data on the 2005 box then - suck it & see fixing any issues (IF there are any) in testing.
Or you could spend your life reading up on the possible failures & effects that may occur as Satya suggests
GWsql
Subscribe to:
Posts (Atom)