Hi,
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon to
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.
SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.
|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which features
> you need. IMHO a decent application with 20 or fewer users should work just
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> to
> a
>
>
|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
>
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to[vbcol=seagreen]
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
for[vbcol=seagreen]
features[vbcol=seagreen]
just[vbcol=seagreen]
message[vbcol=seagreen]
near[vbcol=seagreen]
will[vbcol=seagreen]
logon[vbcol=seagreen]
facts?[vbcol=seagreen]
the[vbcol=seagreen]
from[vbcol=seagreen]
it is[vbcol=seagreen]
We[vbcol=seagreen]
Showing posts with label exe. Show all posts
Showing posts with label exe. Show all posts
Wednesday, March 28, 2012
Help for licensing and proper product for us.
Hi,
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
--
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon t
o
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
---
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which featur
es
> you need. IMHO a decent application with 20 or fewer users should work ju
st
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in messa
ge
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> to
> a
>
>|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
> ---
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to[vbcol=seagreen]
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
>
for[vbcol=seagreen]
features[vbcol=seagreen]
just[vbcol=seagreen]
message[vbcol=seagreen]
near[vbcol=seagreen]
will[vbcol=seagreen]
logon[vbcol=seagreen]
facts?[vbcol=seagreen]
the[vbcol=seagreen]
from[vbcol=seagreen]
it is[vbcol=seagreen]
We[vbcol=seagreen]
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
--
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon t
o
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
---
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which featur
es
> you need. IMHO a decent application with 20 or fewer users should work ju
st
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in messa
ge
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> to
> a
>
>|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
> ---
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to[vbcol=seagreen]
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
>
for[vbcol=seagreen]
features[vbcol=seagreen]
just[vbcol=seagreen]
message[vbcol=seagreen]
near[vbcol=seagreen]
will[vbcol=seagreen]
logon[vbcol=seagreen]
facts?[vbcol=seagreen]
the[vbcol=seagreen]
from[vbcol=seagreen]
it is[vbcol=seagreen]
We[vbcol=seagreen]
Help for licensing and proper product for us.
Hi,
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
--
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon to
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
---
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which features
> you need. IMHO a decent application with 20 or fewer users should work just
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> > Hi,
> >
> > I read the licensing page, but still i'm confused ... as always with
> > licensing stuff.
> >
> > I have a VB 6.0 application (.exe) that establish the connection to my
> > Access database, but we might want to switch to SQL Server2000 in a near
> > future.
> >
> > Our situation
> > --
> > Maximum # of users to use my VB application will be 20. That means I will
> > deploy my VB app on 20 computers. BUT my VB application will always logon
> to
> > the database using the same user.
> >
> > What would be the best licensing model for me considering all these facts?
> > 1- Connection established from a VB application interface.
> > 2- 20 computers will run the VB application
> > 3- On the 20 computers running the VB app, the SQL user to establish the
> > connection will always be the same. So only 1 user.
> >
> > Few more users won't use the VB app and will connect to the database from
> > the Entreprise Manager (2-3 users)
> >
> > SQL Server...
> > Entreprise or Standard. I wonder if standard can do the job for us, it is
> a
> > lot cheaper. I think yes. What's the big difference between the two? We
> > don't need the super big thing here.
> >
> >
> > Thanks for helping.
> > Dominic.
>
>|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
> ---
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
> > SQL User = End user for licensing. A license User is not the same as a
> > connection or a login. Count the TOTAL number of users that access the
> > data. That is how many CALs you need. If the CAL cost exceeds a
> > per-processor license, purchase a per-processor license.
> >
> > Your VB application is considered "middleware" or a "user aggregator"
for
> > licensing purposes. As such you remove it from consideration entirely.
> >
> > Enterprise vs. Standard Edition SQL choice should be based on which
features
> > you need. IMHO a decent application with 20 or fewer users should work
just
> > fine on Standard Edition.
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in
message
> > news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> > > Hi,
> > >
> > > I read the licensing page, but still i'm confused ... as always with
> > > licensing stuff.
> > >
> > > I have a VB 6.0 application (.exe) that establish the connection to my
> > > Access database, but we might want to switch to SQL Server2000 in a
near
> > > future.
> > >
> > > Our situation
> > > --
> > > Maximum # of users to use my VB application will be 20. That means I
will
> > > deploy my VB app on 20 computers. BUT my VB application will always
logon
> > to
> > > the database using the same user.
> > >
> > > What would be the best licensing model for me considering all these
facts?
> > > 1- Connection established from a VB application interface.
> > > 2- 20 computers will run the VB application
> > > 3- On the 20 computers running the VB app, the SQL user to establish
the
> > > connection will always be the same. So only 1 user.
> > >
> > > Few more users won't use the VB app and will connect to the database
from
> > > the Entreprise Manager (2-3 users)
> > >
> > > SQL Server...
> > > Entreprise or Standard. I wonder if standard can do the job for us,
it is
> > a
> > > lot cheaper. I think yes. What's the big difference between the two?
We
> > > don't need the super big thing here.
> > >
> > >
> > > Thanks for helping.
> > > Dominic.
> >
> >
> >
I read the licensing page, but still i'm confused ... as always with
licensing stuff.
I have a VB 6.0 application (.exe) that establish the connection to my
Access database, but we might want to switch to SQL Server2000 in a near
future.
Our situation
--
Maximum # of users to use my VB application will be 20. That means I will
deploy my VB app on 20 computers. BUT my VB application will always logon to
the database using the same user.
What would be the best licensing model for me considering all these facts?
1- Connection established from a VB application interface.
2- 20 computers will run the VB application
3- On the 20 computers running the VB app, the SQL user to establish the
connection will always be the same. So only 1 user.
Few more users won't use the VB app and will connect to the database from
the Entreprise Manager (2-3 users)
SQL Server...
Entreprise or Standard. I wonder if standard can do the job for us, it is a
lot cheaper. I think yes. What's the big difference between the two? We
don't need the super big thing here.
Thanks for helping.
Dominic.SQL User = End user for licensing. A license User is not the same as a
connection or a login. Count the TOTAL number of users that access the
data. That is how many CALs you need. If the CAL cost exceeds a
per-processor license, purchase a per-processor license.
Your VB application is considered "middleware" or a "user aggregator" for
licensing purposes. As such you remove it from consideration entirely.
Enterprise vs. Standard Edition SQL choice should be based on which features
you need. IMHO a decent application with 20 or fewer users should work just
fine on Standard Edition.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> Hi,
> I read the licensing page, but still i'm confused ... as always with
> licensing stuff.
> I have a VB 6.0 application (.exe) that establish the connection to my
> Access database, but we might want to switch to SQL Server2000 in a near
> future.
> Our situation
> --
> Maximum # of users to use my VB application will be 20. That means I will
> deploy my VB app on 20 computers. BUT my VB application will always logon
to
> the database using the same user.
> What would be the best licensing model for me considering all these facts?
> 1- Connection established from a VB application interface.
> 2- 20 computers will run the VB application
> 3- On the 20 computers running the VB app, the SQL user to establish the
> connection will always be the same. So only 1 user.
> Few more users won't use the VB app and will connect to the database from
> the Entreprise Manager (2-3 users)
> SQL Server...
> Entreprise or Standard. I wonder if standard can do the job for us, it is
a
> lot cheaper. I think yes. What's the big difference between the two? We
> don't need the super big thing here.
>
> Thanks for helping.
> Dominic.|||Ok.
So if I have 1 computer accessing the data. But 3 users can be working on
that computer.
The cheaper and legal licensing model for me would be to go with the Server
Plus Device CAL, right? And would only buy 1 license.
-- ON THE OTHER HAND --
If I have 3 computers accessing the data, but only 1 user can be working on
that computer.
Than I would go with the Server Plus User CAL, right? And again would only
buy 1 license.
---
For Server Licensing.
I'm not familiar with SQL Server and won't be my task to administrate it.
But if I want 2 or more instances of database ( Production, QA, Development
). Is this all reside on the same server installation so only 1 server
license is enough.
Or I can only install 1 database on a machine(production) and other(qa &
dev) would need to be on other machine? So I would need 3 server licenses?
I guess I can have multiple instances on only 1 computer, but I only want to
make sure. This technical stuff is not my field of expertise.
Thanks.
"Geoff N. Hiten" wrote:
> SQL User = End user for licensing. A license User is not the same as a
> connection or a login. Count the TOTAL number of users that access the
> data. That is how many CALs you need. If the CAL cost exceeds a
> per-processor license, purchase a per-processor license.
> Your VB application is considered "middleware" or a "user aggregator" for
> licensing purposes. As such you remove it from consideration entirely.
> Enterprise vs. Standard Edition SQL choice should be based on which features
> you need. IMHO a decent application with 20 or fewer users should work just
> fine on Standard Edition.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
> news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> > Hi,
> >
> > I read the licensing page, but still i'm confused ... as always with
> > licensing stuff.
> >
> > I have a VB 6.0 application (.exe) that establish the connection to my
> > Access database, but we might want to switch to SQL Server2000 in a near
> > future.
> >
> > Our situation
> > --
> > Maximum # of users to use my VB application will be 20. That means I will
> > deploy my VB app on 20 computers. BUT my VB application will always logon
> to
> > the database using the same user.
> >
> > What would be the best licensing model for me considering all these facts?
> > 1- Connection established from a VB application interface.
> > 2- 20 computers will run the VB application
> > 3- On the 20 computers running the VB app, the SQL user to establish the
> > connection will always be the same. So only 1 user.
> >
> > Few more users won't use the VB app and will connect to the database from
> > the Entreprise Manager (2-3 users)
> >
> > SQL Server...
> > Entreprise or Standard. I wonder if standard can do the job for us, it is
> a
> > lot cheaper. I think yes. What's the big difference between the two? We
> > don't need the super big thing here.
> >
> >
> > Thanks for helping.
> > Dominic.
>
>|||I would call your local Microsoft office and ask to speak to a sales and
licensing person. They are the only ones that have the 'Legal and Official"
answers.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in message
news:B453E6CD-E0F7-4205-BB39-53D1D16D5778@.microsoft.com...
> Ok.
> So if I have 1 computer accessing the data. But 3 users can be working on
> that computer.
> The cheaper and legal licensing model for me would be to go with the
Server
> Plus Device CAL, right? And would only buy 1 license.
> -- ON THE OTHER HAND --
> If I have 3 computers accessing the data, but only 1 user can be working
on
> that computer.
> Than I would go with the Server Plus User CAL, right? And again would
only
> buy 1 license.
> ---
> For Server Licensing.
> I'm not familiar with SQL Server and won't be my task to administrate it.
> But if I want 2 or more instances of database ( Production, QA,
Development
> ). Is this all reside on the same server installation so only 1 server
> license is enough.
> Or I can only install 1 database on a machine(production) and other(qa &
> dev) would need to be on other machine? So I would need 3 server
licenses?
> I guess I can have multiple instances on only 1 computer, but I only want
to
> make sure. This technical stuff is not my field of expertise.
> Thanks.
>
> "Geoff N. Hiten" wrote:
> > SQL User = End user for licensing. A license User is not the same as a
> > connection or a login. Count the TOTAL number of users that access the
> > data. That is how many CALs you need. If the CAL cost exceeds a
> > per-processor license, purchase a per-processor license.
> >
> > Your VB application is considered "middleware" or a "user aggregator"
for
> > licensing purposes. As such you remove it from consideration entirely.
> >
> > Enterprise vs. Standard Edition SQL choice should be based on which
features
> > you need. IMHO a decent application with 20 or fewer users should work
just
> > fine on Standard Edition.
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "dbelley_office" <dbelley_office@.discussions.microsoft.com> wrote in
message
> > news:F93D8030-77CD-4EDE-87D6-D05BCC44DBF3@.microsoft.com...
> > > Hi,
> > >
> > > I read the licensing page, but still i'm confused ... as always with
> > > licensing stuff.
> > >
> > > I have a VB 6.0 application (.exe) that establish the connection to my
> > > Access database, but we might want to switch to SQL Server2000 in a
near
> > > future.
> > >
> > > Our situation
> > > --
> > > Maximum # of users to use my VB application will be 20. That means I
will
> > > deploy my VB app on 20 computers. BUT my VB application will always
logon
> > to
> > > the database using the same user.
> > >
> > > What would be the best licensing model for me considering all these
facts?
> > > 1- Connection established from a VB application interface.
> > > 2- 20 computers will run the VB application
> > > 3- On the 20 computers running the VB app, the SQL user to establish
the
> > > connection will always be the same. So only 1 user.
> > >
> > > Few more users won't use the VB app and will connect to the database
from
> > > the Entreprise Manager (2-3 users)
> > >
> > > SQL Server...
> > > Entreprise or Standard. I wonder if standard can do the job for us,
it is
> > a
> > > lot cheaper. I think yes. What's the big difference between the two?
We
> > > don't need the super big thing here.
> > >
> > >
> > > Thanks for helping.
> > > Dominic.
> >
> >
> >
Friday, March 23, 2012
help docs for osql.exe parameters
Where can I find help files (.CHM) or other docs on the use of the various
osql.exe command line parameters ?BOL ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"John Grandy" <johnagrandy-at-yahoo-dot-com> schrieb im Newsbeitrag
news:udO%236FGbFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Where can I find help files (.CHM) or other docs on the use of the various
> osql.exe command line parameters ?
>|||http://msdn.microsoft.com/library/d...br />
1wxl.asp
"John Grandy" wrote:
> Where can I find help files (.CHM) or other docs on the use of the various
> osql.exe command line parameters ?
>
>|||osql /?
--
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/
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:u8oRuNGbFHA.3032@.TK2MSFTNGP10.phx.gbl...
> BOL ?
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "John Grandy" <johnagrandy-at-yahoo-dot-com> schrieb im Newsbeitrag
> news:udO%236FGbFHA.3932@.TK2MSFTNGP12.phx.gbl...
>|||Hi Mike, and thanks for the response.
Yes, osql -? gives the list of parameters, but isn't there some way to
interactively get help on each parameter?
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23GhhXlGbFHA.3144@.TK2MSFTNGP14.phx.gbl...
> osql /?
> --
> --
> 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/
> "Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
> in message news:u8oRuNGbFHA.3032@.TK2MSFTNGP10.phx.gbl...
>|||In addition to the copy of the Books Online in MSDN that Cris linked to, you
can download a local copy from:
http://www.microsoft.com/downloads/...&displaylang=en
Alan Brewer [MSFT]
Content Architect
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights.|||at the command prompt type:
osql /?
"John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:udO%236FGbFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Where can I find help files (.CHM) or other docs on the use of the various
> osql.exe command line parameters ?
>|||Not from the SQL Server command prompt utilities like osql. The GUI tools
have their F1 help linked into topics in the Books Online, but not the
command prompt utilities. You get the short list from the utility itself if
you use the /? switch, and you get the more in-depth help from the Books
Online osql reference topic, either online in the MSDN Library or your local
copy.
Alan Brewer [MSFT]
Content Architect
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights.
osql.exe command line parameters ?BOL ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"John Grandy" <johnagrandy-at-yahoo-dot-com> schrieb im Newsbeitrag
news:udO%236FGbFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Where can I find help files (.CHM) or other docs on the use of the various
> osql.exe command line parameters ?
>|||http://msdn.microsoft.com/library/d...br />
1wxl.asp
"John Grandy" wrote:
> Where can I find help files (.CHM) or other docs on the use of the various
> osql.exe command line parameters ?
>
>|||osql /?
--
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/
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:u8oRuNGbFHA.3032@.TK2MSFTNGP10.phx.gbl...
> BOL ?
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "John Grandy" <johnagrandy-at-yahoo-dot-com> schrieb im Newsbeitrag
> news:udO%236FGbFHA.3932@.TK2MSFTNGP12.phx.gbl...
>|||Hi Mike, and thanks for the response.
Yes, osql -? gives the list of parameters, but isn't there some way to
interactively get help on each parameter?
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23GhhXlGbFHA.3144@.TK2MSFTNGP14.phx.gbl...
> osql /?
> --
> --
> 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/
> "Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
> in message news:u8oRuNGbFHA.3032@.TK2MSFTNGP10.phx.gbl...
>|||In addition to the copy of the Books Online in MSDN that Cris linked to, you
can download a local copy from:
http://www.microsoft.com/downloads/...&displaylang=en
Alan Brewer [MSFT]
Content Architect
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights.|||at the command prompt type:
osql /?
"John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:udO%236FGbFHA.3932@.TK2MSFTNGP12.phx.gbl...
> Where can I find help files (.CHM) or other docs on the use of the various
> osql.exe command line parameters ?
>|||Not from the SQL Server command prompt utilities like osql. The GUI tools
have their F1 help linked into topics in the Books Online, but not the
command prompt utilities. You get the short list from the utility itself if
you use the /? switch, and you get the more in-depth help from the Books
Online osql reference topic, either online in the MSDN Library or your local
copy.
Alan Brewer [MSFT]
Content Architect
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 7, 2012
Help - Rebuild System Databases on a clustered instance
I am in a DR senario and I am having trouble rebuilding the system databases on my SQL 2005 cluster.
I run the following string:
start /wait setup.exe /qn VS=Vname INSTANCENAME=instname REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=password SQLACCOUNT=domain\acct SQLPASSWORD=password AGTACCOUNT=domain\acct AGTPASSWORD=password REINSTALLMODE=vomus
The setup fails with the following error:
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows Server 2003 family, Service Pack 1 (Build 3790)
Time : Wed Dec 13 15:41:44 2006
CLUSTERSVR1 : To install Microsoft SQL Server 2005, COM+ should work.
CLUSTERSVR1 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
CLUSTERSVR1 : To install Microsoft SQL Server 2005, COM+ should work.
CLUSTERSVR1 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine : CLUSTERSVR1
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Error Number : 5897
SQL 2005 was originally installed in May '06 as RTM. SP1 applied in September '06.
I have the original RTM install disk but obviously SP1 is causing rebuild to fail.
Can anyone advise on this please.
D.
Can you apply SP1 and then retry the procedure?
I mean doing the setup of 2005, applying SP1 and then retrying?
|||JohDas,
Unfortunately I can't.
Don't forget I do not have any databases - system or user. Therefore SP1 cannot authenticate to SQL Server to process the upgrade.
I have a bad feeling that my only option is to uninstall/reinstall SQL 2005.
But this is a last resort and I want to avaoid it if I can.
D.
Friday, February 24, 2012
Help
I've tried to install MDAC only at Win 98 (MDAC_TYP.EXE). But my program is
still not able to work. My Program use ADO to connect SQL Server 2000. So
what do i need to install again to my program can work/run?Why is it not working, do you get an error message for it ?
--
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Bpk. Adi Wira Kusuma" wrote:
> I've tried to install MDAC only at Win 98 (MDAC_TYP.EXE). But my program
is
> still not able to work. My Program use ADO to connect SQL Server 2000. So
> what do i need to install again to my program can work/run?
>
>|||wehhh, I'm forget its error message. But I sure that I don't install
complettely. Nah... I just ask to you, What Any kind of which need to be
installed So My app. can work / running?|||You just need to install the MDAC:
http://www.microsoft.com/downloads/...&displaylang=en
What kind of application do you want to deploy ?
--
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Bpk. Adi Wira Kusuma" wrote:
> wehhh, I'm forget its error message. But I sure that I don't install
> complettely. Nah... I just ask to you, What Any kind of which need to be
> installed So My app. can work / running?
>
>
still not able to work. My Program use ADO to connect SQL Server 2000. So
what do i need to install again to my program can work/run?Why is it not working, do you get an error message for it ?
--
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Bpk. Adi Wira Kusuma" wrote:
> I've tried to install MDAC only at Win 98 (MDAC_TYP.EXE). But my program
is
> still not able to work. My Program use ADO to connect SQL Server 2000. So
> what do i need to install again to my program can work/run?
>
>|||wehhh, I'm forget its error message. But I sure that I don't install
complettely. Nah... I just ask to you, What Any kind of which need to be
installed So My app. can work / running?|||You just need to install the MDAC:
http://www.microsoft.com/downloads/...&displaylang=en
What kind of application do you want to deploy ?
--
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Bpk. Adi Wira Kusuma" wrote:
> wehhh, I'm forget its error message. But I sure that I don't install
> complettely. Nah... I just ask to you, What Any kind of which need to be
> installed So My app. can work / running?
>
>
Subscribe to:
Posts (Atom)