Showing posts with label workgroup. Show all posts
Showing posts with label workgroup. Show all posts

Wednesday, March 28, 2012

MS sql server on workgroup not domain.

Hi have a small network setup and have MS sql server on workstation.
Can access it locally but cannot access it from other work stations.
I am assuming it is some sort of logon error, being it is not a
domain. Any ideas on getting by this ?Two possible issues.

One it's installed on Win XP with service pack 2. SP2 has an automatic
firewall that you will need to punch a hole through.

Two the SQL Server is configured for Windows only authentication. Since you
can access it locally you are probably a member of the local administrators
group and as such are granted sa rights by default. Windows only
authentication will not work for remote connections in a work group. You
will need to use SQL Server standard security in mixed mode.

Hope this helps,
Danny

"Father Jack Hackett" <Jachack@.rcc.org> wrote in message
news:j8r4q0djmla88go6hdbraesv6nl4n4d3cd@.4ax.com...
> Hi have a small network setup and have MS sql server on workstation.
> Can access it locally but cannot access it from other work stations.
> I am assuming it is some sort of logon error, being it is not a
> domain. Any ideas on getting by this ?|||I have been trying to set it up on a local workgroup with all XP home
edition computers, I am running into the same problem.

Lionel

On Tue, 23 Nov 2004 12:45:16 GMT, "Danny" <istdrs@.flash.net> wrote:

>Two possible issues.
>One it's installed on Win XP with service pack 2. SP2 has an automatic
>firewall that you will need to punch a hole through.
>Two the SQL Server is configured for Windows only authentication. Since you
>can access it locally you are probably a member of the local administrators
>group and as such are granted sa rights by default. Windows only
>authentication will not work for remote connections in a work group. You
>will need to use SQL Server standard security in mixed mode.
>Hope this helps,
>Danny
>
>"Father Jack Hackett" <Jachack@.rcc.org> wrote in message
>news:j8r4q0djmla88go6hdbraesv6nl4n4d3cd@.4ax.com...
>> Hi have a small network setup and have MS sql server on workstation.
>> Can access it locally but cannot access it from other work stations.
>> I am assuming it is some sort of logon error, being it is not a
>> domain. Any ideas on getting by this ?

Wednesday, March 7, 2012

MS SQL 2005 Workgroup licensing question

Hi,
I am a bit confused about the licensing schemes for MS SQL.
There is a "Processor" licnese (about $4000) and a "Server +
User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
It says:
Processor Licensing Model. Under this model, a license is required for
each physical or virtual processor accessed by an operating system
environment running SQL Server. This license does not require any
device or user client access licenses (CALs).
Server plus Device CALs. Under this model, a server license is required
for each operating system environment running an instance of SQL
Server, as well as a CAL for each client device that accesses a system
running SQL Server.
Server plus User CALs. Under this model, a server license is required
for each operating system environment running an instance of SQL
Server, as well as a CAL for each user that accesses a system running
SQL Server.
If I am installing the MS SQL on one web server running Windows 2003
Server, accessible by corporate users over Internet, which licensing
model is suitable?
TIA.Calculate how many different users access the server. Not at once,
all together over time. Calculate the cost of that many CALs compared
to the per-processor price. You probably will end up with
per-processor pricing.
Roy Harvey
Beacon Falls, CT
On 26 Jul 2006 10:03:32 -0700, ashkaan57@.hotmail.com wrote:

>Hi,
>I am a bit confused about the licensing schemes for MS SQL.
>There is a "Processor" licnese (about $4000) and a "Server +
>User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
>It says:
>Processor Licensing Model. Under this model, a license is required for
>each physical or virtual processor accessed by an operating system
>environment running SQL Server. This license does not require any
>device or user client access licenses (CALs).
>Server plus Device CALs. Under this model, a server license is required
>for each operating system environment running an instance of SQL
>Server, as well as a CAL for each client device that accesses a system
>running SQL Server.
>Server plus User CALs. Under this model, a server license is required
>for each operating system environment running an instance of SQL
>Server, as well as a CAL for each user that accesses a system running
>SQL Server.
>If I am installing the MS SQL on one web server running Windows 2003
>Server, accessible by corporate users over Internet, which licensing
>model is suitable?
>TIA.|||The definitive answers to licensing questions are at:
http://www.microsoft.com/licensing/default.mspx
My take:
You may recall, that the processor license is required for
internet/intranet/extranet usage UNLESS all users will have a proper CAL.
(That even includes a single small query populating a small list box on a
web page.)
If your web site is restricted to company users only, and if all company
users that will be accessing SQL Server have an existing SQL Server CAL,
then I believe that you are covered. (Subject to verification with VL.) If
all company users do not have SQL Server CALs, then you most likely need a
processor license -or additional CALs.
I do not think that any non-company (or extranet) users would be included
without the processor license -unless, upon software audit, you can prove
the existence of CALs.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<ashkaan57@.hotmail.com> wrote in message
news:1153933412.130178.59290@.s13g2000cwa.googlegroups.com...
> Hi,
> I am a bit confused about the licensing schemes for MS SQL.
> There is a "Processor" licnese (about $4000) and a "Server +
> User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
> It says:
> Processor Licensing Model. Under this model, a license is required for
> each physical or virtual processor accessed by an operating system
> environment running SQL Server. This license does not require any
> device or user client access licenses (CALs).
> Server plus Device CALs. Under this model, a server license is required
> for each operating system environment running an instance of SQL
> Server, as well as a CAL for each client device that accesses a system
> running SQL Server.
> Server plus User CALs. Under this model, a server license is required
> for each operating system environment running an instance of SQL
> Server, as well as a CAL for each user that accesses a system running
> SQL Server.
> If I am installing the MS SQL on one web server running Windows 2003
> Server, accessible by corporate users over Internet, which licensing
> model is suitable?
> TIA.
>

MS SQL 2005 Workgroup licensing question

Hi,
I am a bit confused about the licensing schemes for MS SQL.
There is a "Processor" licnese (about $4000) and a "Server +
User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
It says:
Processor Licensing Model. Under this model, a license is required for
each physical or virtual processor accessed by an operating system
environment running SQL Server. This license does not require any
device or user client access licenses (CALs).
Server plus Device CALs. Under this model, a server license is required
for each operating system environment running an instance of SQL
Server, as well as a CAL for each client device that accesses a system
running SQL Server.
Server plus User CALs. Under this model, a server license is required
for each operating system environment running an instance of SQL
Server, as well as a CAL for each user that accesses a system running
SQL Server.
If I am installing the MS SQL on one web server running Windows 2003
Server, accessible by corporate users over Internet, which licensing
model is suitable?
TIA.Calculate how many different users access the server. Not at once,
all together over time. Calculate the cost of that many CALs compared
to the per-processor price. You probably will end up with
per-processor pricing.
Roy Harvey
Beacon Falls, CT
On 26 Jul 2006 10:03:32 -0700, ashkaan57@.hotmail.com wrote:
>Hi,
>I am a bit confused about the licensing schemes for MS SQL.
>There is a "Processor" licnese (about $4000) and a "Server +
>User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
>It says:
>Processor Licensing Model. Under this model, a license is required for
>each physical or virtual processor accessed by an operating system
>environment running SQL Server. This license does not require any
>device or user client access licenses (CALs).
>Server plus Device CALs. Under this model, a server license is required
>for each operating system environment running an instance of SQL
>Server, as well as a CAL for each client device that accesses a system
>running SQL Server.
>Server plus User CALs. Under this model, a server license is required
>for each operating system environment running an instance of SQL
>Server, as well as a CAL for each user that accesses a system running
>SQL Server.
>If I am installing the MS SQL on one web server running Windows 2003
>Server, accessible by corporate users over Internet, which licensing
>model is suitable?
>TIA.|||The definitive answers to licensing questions are at:
http://www.microsoft.com/licensing/default.mspx
My take:
You may recall, that the processor license is required for
internet/intranet/extranet usage UNLESS all users will have a proper CAL.
(That even includes a single small query populating a small list box on a
web page.)
If your web site is restricted to company users only, and if all company
users that will be accessing SQL Server have an existing SQL Server CAL,
then I believe that you are covered. (Subject to verification with VL.) If
all company users do not have SQL Server CALs, then you most likely need a
processor license -or additional CALs.
I do not think that any non-company (or extranet) users would be included
without the processor license -unless, upon software audit, you can prove
the existence of CALs.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<ashkaan57@.hotmail.com> wrote in message
news:1153933412.130178.59290@.s13g2000cwa.googlegroups.com...
> Hi,
> I am a bit confused about the licensing schemes for MS SQL.
> There is a "Processor" licnese (about $4000) and a "Server +
> User/Device CAL" for $740 (5 CALs + $150 per additional CAL).
> It says:
> Processor Licensing Model. Under this model, a license is required for
> each physical or virtual processor accessed by an operating system
> environment running SQL Server. This license does not require any
> device or user client access licenses (CALs).
> Server plus Device CALs. Under this model, a server license is required
> for each operating system environment running an instance of SQL
> Server, as well as a CAL for each client device that accesses a system
> running SQL Server.
> Server plus User CALs. Under this model, a server license is required
> for each operating system environment running an instance of SQL
> Server, as well as a CAL for each user that accesses a system running
> SQL Server.
> If I am installing the MS SQL on one web server running Windows 2003
> Server, accessible by corporate users over Internet, which licensing
> model is suitable?
> TIA.
>