Calculated measures on Analysis server

Hi,

Is there anyway I can process calculated measures of the cube on server? As of now its getting processed on client and its taking lot of client memory. We have got a good configuration server. Is there anyway I can configure to get this processing done on OLAP server?

Any help/tip will be appreciated

Thanks,
SP

Are you alluding to MDX query processing, and are you using AS 2000 or AS 2005?|||

Hi Deepak,

We are usin AS2000. What exactly u mean by alluding by "alluding to MDX query processing"?

Thanks

|||

Just wanted to confirm that you weren't referring to cube processing time, rather than to query response time.

With AS 2000, you can (to some extent) increase server-side query execution by changing connection string parameters:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ansvcspg.mspx

>>

Microsoft SQL Server 2000 Analysis Services Performance Guide

Published: June 1, 2003

By Carl Rabeler, Len Wyatt, Dave Wickert

Summary: This paper describes techniques you can use to optimize query responsiveness and processing performance in Microsoft? SQL Server? 2000 Analysis Services.

...

The Execution Location and Default Isolation Mode properties are always used together.

The Execution Location property controls whether a query is executed on the client or on the Analysis server. By default, the execution of the query is split between the client and the server in order to distribute the processing load across multiple computers. Using an Execution Location setting of 3 in the connection string causes most queries to be executed on the Analysis server. This setting also reduces the amount of data that is returned to the client over a slow network connection. In most cases, only the final result is returned to the client, and the client processor resources are not used to help resolve the query. The value of the Execution Location property is set in the connection string when a session is established. It can be changed during the session. However, every client using this setting adds to the load on the Analysis server.

The Default Isolation Mode property controls the refreshing of the cache on the client. Using a Default Isolation Mode setting of 1 causes the cache to be invalidated whenever a query statement is executed. When this setting is used in conjunction with the Execution Location setting of 3, you can ensure that most queries are resolved on the Analysis server rather than at the client. By default, PTS will use data in the local cache to resolve queries when possible, which conflicts with the Execution Location setting if you are attempting to execute as many queries as possible on the Analysis server. The value of the Default Isolation Mode property is set in the connection string when a session is established. This value can also be changed during a session.

>>

|||

Hi Deepak,

Thanks a lot,

This is definitely goigng to help us in our approach

Regards,

SP

Calculated measures on Analysis server

Hi,

Is there anyway I can process calculated measures of the cube on server? As of now its getting processed on client and its taking lot of client memory. We have got a good configuration server. Is there anyway I can configure to get this processing done on OLAP server?

Any help/tip will be appreciated

Thanks,
SP

Are you alluding to MDX query processing, and are you using AS 2000 or AS 2005?|||

Hi Deepak,

We are usin AS2000. What exactly u mean by alluding by "alluding to MDX query processing"?

Thanks

|||

Just wanted to confirm that you weren't referring to cube processing time, rather than to query response time.

With AS 2000, you can (to some extent) increase server-side query execution by changing connection string parameters:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ansvcspg.mspx

>>

Microsoft SQL Server 2000 Analysis Services Performance Guide

Published: June 1, 2003

By Carl Rabeler, Len Wyatt, Dave Wickert

Summary: This paper describes techniques you can use to optimize query responsiveness and processing performance in Microsoft? SQL Server? 2000 Analysis Services.

...

The Execution Location and Default Isolation Mode properties are always used together.

The Execution Location property controls whether a query is executed on the client or on the Analysis server. By default, the execution of the query is split between the client and the server in order to distribute the processing load across multiple computers. Using an Execution Location setting of 3 in the connection string causes most queries to be executed on the Analysis server. This setting also reduces the amount of data that is returned to the client over a slow network connection. In most cases, only the final result is returned to the client, and the client processor resources are not used to help resolve the query. The value of the Execution Location property is set in the connection string when a session is established. It can be changed during the session. However, every client using this setting adds to the load on the Analysis server.

The Default Isolation Mode property controls the refreshing of the cache on the client. Using a Default Isolation Mode setting of 1 causes the cache to be invalidated whenever a query statement is executed. When this setting is used in conjunction with the Execution Location setting of 3, you can ensure that most queries are resolved on the Analysis server rather than at the client. By default, PTS will use data in the local cache to resolve queries when possible, which conflicts with the Execution Location setting if you are attempting to execute as many queries as possible on the Analysis server. The value of the Default Isolation Mode property is set in the connection string when a session is established. This value can also be changed during a session.

>>

|||

Hi Deepak,

Thanks a lot,

This is definitely goigng to help us in our approach

Regards,

SP

Calculated Column performance

Hi,
Is calulation more efficent in the SQL CODE or in a Calculated Column? If
I'm correct the Calculated Column is done on the client SELECT query every
time where as my INSERT TSQL code will only do it once on the INSERT?
Thanks
DECLARE
@.ACCDCC_Table TABLE
(cnt INT NULL,
Time INT NULL,
Location FLOAT NULL,
FPM1 FLOAT NULL,
FPM2 FLOAT NULL,
FPM_Diff AS (
CASE
WHEN
FPM1 IS NULL OR
FPM2 IS NULL THEN NULL
ELSE
FPM2 - FPM1
END),
AccDcc VARCHAR(10) NULL
)
as per doing this:
UPDATE
@.ACCDCC_Table
SET
FPM_Diff = FPM2 - FPM1
WHERE
FPM_Diff IS NULL
--
don> Is calulation more efficent in the SQL CODE or in a Calculated Column? If
> I'm correct the Calculated Column is done on the client SELECT query every
> time where as my INSERT TSQL code will only do it once on the INSERT?
That's correct.
The flip side is that you will have to constantly maintain the value in the
"calculated" column if you're going to rely on doing it manually.
A|||Thanks
"AB - MVP" wrote:

> That's correct.
> The flip side is that you will have to constantly maintain the value in th
e
> "calculated" column if you're going to rely on doing it manually.
> A
>
>|||Think you meant you have to maintain it when you are doing it once, on
update. If it's calculated automatically, every time you "select" the
column, the value is not being stored in database, It's being re-calculated
every time you do a select, so there's no maintenance required.
Which is better depends on whether you need
A) Insert/Update Performance, and/Or storage Size Constraints -- Use
Calculated Column, or
B) Select Performance is the main concern -- Then Use persisted Column and
maintain it upon every Insert/Update
"AB - MVP" wrote:

> That's correct.
> The flip side is that you will have to constantly maintain the value in th
e
> "calculated" column if you're going to rely on doing it manually.
> A
>
>|||Thanks
"CBretana" wrote:
> Think you meant you have to maintain it when you are doing it once, on
> update. If it's calculated automatically, every time you "select" the
> column, the value is not being stored in database, It's being re-calculate
d
> every time you do a select, so there's no maintenance required.
> Which is better depends on whether you need
> A) Insert/Update Performance, and/Or storage Size Constraints -- Use
> Calculated Column, or
> B) Select Performance is the main concern -- Then Use persisted Column and
> maintain it upon every Insert/Update
> "AB - MVP" wrote:
>|||I guess someone missed the meaning of "quotes" around "calculated"... <sigh>
"donron" <donron@.discussions.microsoft.com> wrote in message
news:2CCDA1CD-B43E-4D0E-AEFF-6C77615F5755@.microsoft.com...
> Thanks
> "CBretana" wrote:
>|||that would be me... but rereading, (I may be just dense this am), but I'm
still not sure what you mean by it... I thought it was just a typo...
"AB - MVP" wrote:

> I guess someone missed the meaning of "quotes" around "calculated"... <sig
h>
>
>
> "donron" <donron@.discussions.microsoft.com> wrote in message
> news:2CCDA1CD-B43E-4D0E-AEFF-6C77615F5755@.microsoft.com...
>
>

Calculated cells in Excel?

Hi,
We're evaluating Reporting Services for a client. I like the functionality,
but it's unclear whether we can manipulate Excel output. For example, our
client will want to generate or populate a spreadsheet that has multiple
worksheets, with calculated values that pull values from one or more of
those sheets.
Does RS support this level of complexity?
Thanks in advance,
Ian LurieI don't know about creating calculated fields, but you can put tables
onto different sheets by setting the page break after table property
to true. The only reporting product I have seen that allows you to
export formulas is actuate. Should you find a way to do it with
reporting services, *please* let me know! We are interested in it
too-
Thanks,
John Hennesey
johnhennesey82@.hotmail.com
"Ian Lurie" <ian@.portentinteractive.com> wrote in message news:<#eXuLqRXEHA.1356@.TK2MSFTNGP09.phx.gbl>...
> Hi,
> We're evaluating Reporting Services for a client. I like the functionality,
> but it's unclear whether we can manipulate Excel output. For example, our
> client will want to generate or populate a spreadsheet that has multiple
> worksheets, with calculated values that pull values from one or more of
> those sheets.
> Does RS support this level of complexity?
> Thanks in advance,
> Ian Lurie|||We export formulas as along as they contain only report item references.
--
Nico Cristache [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Hennesey" <johnhennesey82@.hotmail.com> wrote in message
news:9f049b3b.0406281103.54baf474@.posting.google.com...
> I don't know about creating calculated fields, but you can put tables
> onto different sheets by setting the page break after table property
> to true. The only reporting product I have seen that allows you to
> export formulas is actuate. Should you find a way to do it with
> reporting services, *please* let me know! We are interested in it
> too-
> Thanks,
> John Hennesey
> johnhennesey82@.hotmail.com
> "Ian Lurie" <ian@.portentinteractive.com> wrote in message
news:<#eXuLqRXEHA.1356@.TK2MSFTNGP09.phx.gbl>...
> > Hi,
> >
> > We're evaluating Reporting Services for a client. I like the
functionality,
> > but it's unclear whether we can manipulate Excel output. For example,
our
> > client will want to generate or populate a spreadsheet that has multiple
> > worksheets, with calculated values that pull values from one or more of
> > those sheets.
> >
> > Does RS support this level of complexity?
> >
> > Thanks in advance,
> >
> > Ian Luriesql

CAL license required?

Microsoft SQL Server 2000 client access license (CAL) licensing terms
states:
A SQL Server CAL is required for a device (for example, a personal
computer, workstation, terminal, personal digital assistant, or
mobile phone) to access or use the services or functionality of
either edition of SQL Server.
I have an application (exe) that accepts TCP/IP connections and stores
the IP addresses of the connecting computers or other devices to a table
stored at SQL Server 2000 Standard Edition database.
Do I have to have a CAL license for every connecting device?
I have an application (exe) that monitors caller numbers from a standard
phone line and stores the caller numbers to a table stored at SQL Server
2000 Standard Edition database.
Do I have to have a CAL license for every calling phone?
SQL Server 2000 CAL licence information can be found at
http://www.microsoft.com/sql/howtobuy/servercal.asp .
Microsoft license information makes it sound like any data that ever passed
through a SQL Server database at some stage in its life has to have a CAL.
We have all been assimilated now...
"JF" <noone@.nowhere.com> wrote in message
news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms
> states:
> A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
> I have an application (exe) that accepts TCP/IP connections and stores
> the IP addresses of the connecting computers or other devices to a table
> stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
> I have an application (exe) that monitors caller numbers from a standard
> phone line and stores the caller numbers to a table stored at SQL Server
> 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
> SQL Server 2000 CAL licence information can be found at
> http://www.microsoft.com/sql/howtobuy/servercal.asp .
>
|||Licensing is a very complex beast, but I would guess that for the TCP/IP =
application you would need a CAL for each device that connects. This =
scenario sounds a bit like an internet app (or a multiplexed app), =
therefore you might have to the the per processor licensing route. =20
In the phone case I would guess that you only need one CAL (for the =
exe/phone combination) because you are only logging data as collected by =
your phone line and the exe. This scenario sounds like a service that =
monitors and log events to your database. =20
The difference is slight, but the first scenario has clients connecting =
to it (and to SQL Server). The second example is more like a monitor =
that you have in place.
Don't take my assumptions as right or wrong, they are only a guess.
--=20
Keith
"JF" <noone@.nowhere.com> wrote in message =
news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms=20
> states:
>=20
> A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
>=20
> I have an application (exe) that accepts TCP/IP connections and stores =

> the IP addresses of the connecting computers or other devices to a =
table=20
> stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
>=20
> I have an application (exe) that monitors caller numbers from a =
standard=20
> phone line and stores the caller numbers to a table stored at SQL =
Server=20
> 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
>=20
> SQL Server 2000 CAL licence information can be found at=20
> http://www.microsoft.com/sql/howtobuy/servercal.asp .
>
|||If I am reading this correctly you have an application that when other
applications attach to it the first logs the IP address of the second. Does
the second application (or device) then extract data from the database or is
some other process done? If the purpose of the database is to store the IP
addresses captured by the first application you need a CAL for each machine
running that application. in the case of the second scenario you would need
one CAL for the machine running the phone number capturing application and
any other machine involved in extracting that information from the database.
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"JF" <noone@.nowhere.com> wrote in message
news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms
> states:
> A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
> I have an application (exe) that accepts TCP/IP connections and stores
> the IP addresses of the connecting computers or other devices to a table
> stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
> I have an application (exe) that monitors caller numbers from a standard
> phone line and stores the caller numbers to a table stored at SQL Server
> 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
> SQL Server 2000 CAL licence information can be found at
> http://www.microsoft.com/sql/howtobuy/servercal.asp .
>

CAL license required?

Microsoft SQL Server 2000 client access license (CAL) licensing terms
states:
A SQL Server CAL is required for a device (for example, a personal
computer, workstation, terminal, personal digital assistant, or
mobile phone) to access or use the services or functionality of
either edition of SQL Server.
I have an application (exe) that accepts TCP/IP connections and stores
the IP addresses of the connecting computers or other devices to a table
stored at SQL Server 2000 Standard Edition database.
Do I have to have a CAL license for every connecting device?
I have an application (exe) that monitors caller numbers from a standard
phone line and stores the caller numbers to a table stored at SQL Server
2000 Standard Edition database.
Do I have to have a CAL license for every calling phone?
SQL Server 2000 CAL licence information can be found at
http://www.microsoft.com/sql/howtobuy/servercal.asp .Microsoft license information makes it sound like any data that ever passed
through a SQL Server database at some stage in its life has to have a CAL.
We have all been assimilated now...
"JF" <noone@.nowhere.com> wrote in message
news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms
> states:
> A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
> I have an application (exe) that accepts TCP/IP connections and stores
> the IP addresses of the connecting computers or other devices to a table
> stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
> I have an application (exe) that monitors caller numbers from a standard
> phone line and stores the caller numbers to a table stored at SQL Server
> 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
> SQL Server 2000 CAL licence information can be found at
> http://www.microsoft.com/sql/howtobuy/servercal.asp .
>|||Licensing is a very complex beast, but I would guess that for the TCP/IP =application you would need a CAL for each device that connects. This =scenario sounds a bit like an internet app (or a multiplexed app), =therefore you might have to the the per processor licensing route.
In the phone case I would guess that you only need one CAL (for the =exe/phone combination) because you are only logging data as collected by =your phone line and the exe. This scenario sounds like a service that =monitors and log events to your database.
The difference is slight, but the first scenario has clients connecting =to it (and to SQL Server). The second example is more like a monitor =that you have in place.
Don't take my assumptions as right or wrong, they are only a guess.
-- Keith
"JF" <noone@.nowhere.com> wrote in message =news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms > states:
> > A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
> > I have an application (exe) that accepts TCP/IP connections and stores =
> the IP addresses of the connecting computers or other devices to a =table > stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
> > I have an application (exe) that monitors caller numbers from a =standard > phone line and stores the caller numbers to a table stored at SQL =Server > 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
> > SQL Server 2000 CAL licence information can be found at > http://www.microsoft.com/sql/howtobuy/servercal.asp .
>|||If I am reading this correctly you have an application that when other
applications attach to it the first logs the IP address of the second. Does
the second application (or device) then extract data from the database or is
some other process done? If the purpose of the database is to store the IP
addresses captured by the first application you need a CAL for each machine
running that application. in the case of the second scenario you would need
one CAL for the machine running the phone number capturing application and
any other machine involved in extracting that information from the database.
--
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"JF" <noone@.nowhere.com> wrote in message
news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms
> states:
> A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
> I have an application (exe) that accepts TCP/IP connections and stores
> the IP addresses of the connecting computers or other devices to a table
> stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
> I have an application (exe) that monitors caller numbers from a standard
> phone line and stores the caller numbers to a table stored at SQL Server
> 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
> SQL Server 2000 CAL licence information can be found at
> http://www.microsoft.com/sql/howtobuy/servercal.asp .
>

CAL license required?

Microsoft SQL Server 2000 client access license (CAL) licensing terms
states:
A SQL Server CAL is required for a device (for example, a personal
computer, workstation, terminal, personal digital assistant, or
mobile phone) to access or use the services or functionality of
either edition of SQL Server.
I have an application (exe) that accepts TCP/IP connections and stores
the IP addresses of the connecting computers or other devices to a table
stored at SQL Server 2000 Standard Edition database.
Do I have to have a CAL license for every connecting device?
I have an application (exe) that monitors caller numbers from a standard
phone line and stores the caller numbers to a table stored at SQL Server
2000 Standard Edition database.
Do I have to have a CAL license for every calling phone?
SQL Server 2000 CAL licence information can be found at
http://www.microsoft.com/sql/howtobuy/servercal.asp .Microsoft license information makes it sound like any data that ever passed
through a SQL Server database at some stage in its life has to have a CAL.
We have all been assimilated now...
"JF" <noone@.nowhere.com> wrote in message
news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms
> states:
> A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
> I have an application (exe) that accepts TCP/IP connections and stores
> the IP addresses of the connecting computers or other devices to a table
> stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
> I have an application (exe) that monitors caller numbers from a standard
> phone line and stores the caller numbers to a table stored at SQL Server
> 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
> SQL Server 2000 CAL licence information can be found at
> http://www.microsoft.com/sql/howtobuy/servercal.asp .
>|||Licensing is a very complex beast, but I would guess that for the TCP/IP =
application you would need a CAL for each device that connects. This =
scenario sounds a bit like an internet app (or a multiplexed app), =
therefore you might have to the the per processor licensing route. =20
In the phone case I would guess that you only need one CAL (for the =
exe/phone combination) because you are only logging data as collected by =
your phone line and the exe. This scenario sounds like a service that =
monitors and log events to your database. =20
The difference is slight, but the first scenario has clients connecting =
to it (and to SQL Server). The second example is more like a monitor =
that you have in place.
Don't take my assumptions as right or wrong, they are only a guess.
--=20
Keith
"JF" <noone@.nowhere.com> wrote in message =
news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms=20
> states:
>=20
> A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
>=20
> I have an application (exe) that accepts TCP/IP connections and stores =

> the IP addresses of the connecting computers or other devices to a =
table=20
> stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
>=20
> I have an application (exe) that monitors caller numbers from a =
standard=20
> phone line and stores the caller numbers to a table stored at SQL =
Server=20
> 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
>=20
> SQL Server 2000 CAL licence information can be found at=20
> http://www.microsoft.com/sql/howtobuy/servercal.asp .
>|||If I am reading this correctly you have an application that when other
applications attach to it the first logs the IP address of the second. Does
the second application (or device) then extract data from the database or is
some other process done? If the purpose of the database is to store the IP
addresses captured by the first application you need a CAL for each machine
running that application. in the case of the second scenario you would need
one CAL for the machine running the phone number capturing application and
any other machine involved in extracting that information from the database.
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"JF" <noone@.nowhere.com> wrote in message
news:%23PARv8VVEHA.3264@.TK2MSFTNGP10.phx.gbl...
> Microsoft SQL Server 2000 client access license (CAL) licensing terms
> states:
> A SQL Server CAL is required for a device (for example, a personal
> computer, workstation, terminal, personal digital assistant, or
> mobile phone) to access or use the services or functionality of
> either edition of SQL Server.
> I have an application (exe) that accepts TCP/IP connections and stores
> the IP addresses of the connecting computers or other devices to a table
> stored at SQL Server 2000 Standard Edition database.
> Do I have to have a CAL license for every connecting device?
> I have an application (exe) that monitors caller numbers from a standard
> phone line and stores the caller numbers to a table stored at SQL Server
> 2000 Standard Edition database.
> Do I have to have a CAL license for every calling phone?
> SQL Server 2000 CAL licence information can be found at
> http://www.microsoft.com/sql/howtobuy/servercal.asp .
>

CAL license Question

If I have a client that is connecting to a report generated by an SQL server
on a web site, does the workstation that is connecting to the web page need
a CAL?.
I would not think so, as the server is doing all of the connecting to the da
tabase, and the client workstation is only viewing the data that was parsed
on the server into the report.
Thanks,You need a processor license.
"Brian Cook" <anonymous@.discussions.microsoft.com> wrote in message
news:C4EDCFAD-BA16-4149-BC37-6BFA688D385F@.microsoft.com...
> If I have a client that is connecting to a report generated by an SQL
server on a web site, does the workstation that is connecting to the web
page need a CAL?.
> I would not think so, as the server is doing all of the connecting to the
database, and the client workstation is only viewing the data that was
parsed on the server into the report.
> Thanks,
>|||Just to clarify. The SQL Server needs the Per Processor License not the
client. The client does not need a license, since the server needs the Per
Processor license.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||So Rand, are you saying that I cannot use the Server Plus Cal version in tha
t instance?
Also if I have a four node cluster, do I need to have a copy of SQL for each
server in the cluster?
Thanks,
-- Rand Boyd [MSFT] wrote: --
Just to clarify. The SQL Server needs the Per Processor License not the
client. The client does not need a license, since the server needs the Per
Processor license.
Rand
This posting is provided "as is" with no warranties and confers no rights.

CAL license Question

If I have a client that is connecting to a report generated by an SQL server on a web site, does the workstation that is connecting to the web page need a CAL?.
I would not think so, as the server is doing all of the connecting to the database, and the client workstation is only viewing the data that was parsed on the server into the report.
Thanks,
You need a processor license.
"Brian Cook" <anonymous@.discussions.microsoft.com> wrote in message
news:C4EDCFAD-BA16-4149-BC37-6BFA688D385F@.microsoft.com...
> If I have a client that is connecting to a report generated by an SQL
server on a web site, does the workstation that is connecting to the web
page need a CAL?.
> I would not think so, as the server is doing all of the connecting to the
database, and the client workstation is only viewing the data that was
parsed on the server into the report.
> Thanks,
>
|||Just to clarify. The SQL Server needs the Per Processor License not the
client. The client does not need a license, since the server needs the Per
Processor license.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||So Rand, are you saying that I cannot use the Server Plus Cal version in that instance?
Also if I have a four node cluster, do I need to have a copy of SQL for each server in the cluster?
Thanks,
-- Rand Boyd [MSFT] wrote: --
Just to clarify. The SQL Server needs the Per Processor License not the
client. The client does not need a license, since the server needs the Per
Processor license.
Rand
This posting is provided "as is" with no warranties and confers no rights.

CAL and POS software

I have a client that is migrating to SQL Server as the D/B for their POS software. The software uses a Pool Manager to exchange data with the D/B. The pool maintains 3 active connections to the D/B per module instance. The POS clients connect to the Po
ol Manager. Considering that their are only 3 connections to SQL per instance, and the POS clients connect to the Pool Manager instead of the SQL D/B, do each of the POS clients still require a CAL or would the server only require CALs to cover the maxim
um Pool D/B connections? Given 3 open modules, this would be a maximum of 9 connections which would require 9 CALs vs. 30. At around $150 per CAL, this could mean a cost difference of $2000 in a SQL+CAL vs. SQL Processor license. Although the obvious i
s to avoid the issue and go for the processor license, $2K is a significant chunk of my client's money in a typically strained budget.
This is what is known as multiplexing and it's explained in the SQL Server
2000 Pricing and Licensing white paper available at
http://www.microsoft.com/sql/howtobu...licensing.asp. The part that
pertains to you is:
MULTIPLEXING: USE OF MIDDLEWARE, TRANSACTION SERVERS, AND MULTI-TIERED
ARCHITECTURES
Sometimes organizations develop network scenarios that use various forms of
hardware and/or software that reduce the number of devices or users that
directly access or utilize the software on a particular server, often called
multiplexing or pooling hardware or software. For example, say a client PC
is using a server application that calls the Microsoft Transaction Server
(MTS) component of Microsoft Windows 2000 Server on one server, which in
turn pulls data from a Microsoft SQL Server database on another server. In
this case, the only direct connection to Microsoft SQL Server is coming from
the server running MTS. The client PC has a direct connection to the server
running MTS, but also has an indirect connection to SQL Server because it is
ultimately retrieving and using the SQL Server data through MTS. Use of such
multiplexing or pooling hardware and/or software does not reduce the number
of CALs required in order to access or utilize SQL Server software. A CAL is
required for each distinct device or user to the multiplexing or pooling
software or hardware front end. If, in the above example, 50 PCs were
connected to the MTS server, 50 SQL Server Device CALs would be required.
This is true no matter how many tiers of hardware or software exist between
the SQL Server and the client devices that ultimately use its data, services
or functionality.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"microchp" <anonymous@.discussions.microsoft.com> wrote in message
news:E090746F-3208-4042-9E35-0554766D6908@.microsoft.com...
> I have a client that is migrating to SQL Server as the D/B for their POS
software. The software uses a Pool Manager to exchange data with the D/B.
The pool maintains 3 active connections to the D/B per module instance. The
POS clients connect to the Pool Manager. Considering that their are only 3
connections to SQL per instance, and the POS clients connect to the Pool
Manager instead of the SQL D/B, do each of the POS clients still require a
CAL or would the server only require CALs to cover the maximum Pool D/B
connections? Given 3 open modules, this would be a maximum of 9 connections
which would require 9 CALs vs. 30. At around $150 per CAL, this could mean
a cost difference of $2000 in a SQL+CAL vs. SQL Processor license. Although
the obvious is to avoid the issue and go for the processor license, $2K is a
significant chunk of my client's money in a typically strained budget.

CAL

I know CAL stands for Client access license, does this mean if I have an
application that logs onto SQL as a generic user, is that one CAL? Do I need
a CAL for each of my application generic users? Des this go for each user I
have in SQL?
TIA,
JoeA CAL covers a connection to the DB, so whether your using a generic login
or user specific logins each is a seperate CAL.|||A CAL covers either a user or a device that connects to SQL. The gotcha is
that only end users or devices count. If you have a web server or other
device that collects end users and feeds them through a single device
connections, then you have to license each end user, not just the single
middle-ware device. Licensed users can have multiple connections so there
is not any relationship between licensed users and connections. If you have
a situation where you cannot enumerate each licensed user, such as a
public-facing web site, then you must license SQLnon a per-processor basis.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:DBCCB86D-7367-4AC5-9B9E-440CA72C31C1@.microsoft.com...
>I know CAL stands for Client access license, does this mean if I have an
> application that logs onto SQL as a generic user, is that one CAL? Do I
> need
> a CAL for each of my application generic users? Des this go for each user
> I
> have in SQL?
> TIA,
> Joe
>|||Thank you.
This was very helpful.
Joe
"Geoff N. Hiten" wrote:
> A CAL covers either a user or a device that connects to SQL. The gotcha is
> that only end users or devices count. If you have a web server or other
> device that collects end users and feeds them through a single device
> connections, then you have to license each end user, not just the single
> middle-ware device. Licensed users can have multiple connections so there
> is not any relationship between licensed users and connections. If you have
> a situation where you cannot enumerate each licensed user, such as a
> public-facing web site, then you must license SQLnon a per-processor basis.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:DBCCB86D-7367-4AC5-9B9E-440CA72C31C1@.microsoft.com...
> >I know CAL stands for Client access license, does this mean if I have an
> > application that logs onto SQL as a generic user, is that one CAL? Do I
> > need
> > a CAL for each of my application generic users? Des this go for each user
> > I
> > have in SQL?
> >
> > TIA,
> > Joe
> >
>
>|||Thank you,
This was very helpful
Joe
"BenUK" wrote:
> A CAL covers a connection to the DB, so whether your using a generic login
> or user specific logins each is a seperate CAL.

CAL

I know CAL stands for Client access license, does this mean if I have an
application that logs onto SQL as a generic user, is that one CAL? Do I nee
d
a CAL for each of my application generic users? Des this go for each user I
have in SQL?
TIA,
JoeA CAL covers a connection to the DB, so whether your using a generic login
or user specific logins each is a seperate CAL.|||A CAL covers either a user or a device that connects to SQL. The gotcha is
that only end users or devices count. If you have a web server or other
device that collects end users and feeds them through a single device
connections, then you have to license each end user, not just the single
middle-ware device. Licensed users can have multiple connections so there
is not any relationship between licensed users and connections. If you have
a situation where you cannot enumerate each licensed user, such as a
public-facing web site, then you must license SQLnon a per-processor basis.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:DBCCB86D-7367-4AC5-9B9E-440CA72C31C1@.microsoft.com...
>I know CAL stands for Client access license, does this mean if I have an
> application that logs onto SQL as a generic user, is that one CAL? Do I
> need
> a CAL for each of my application generic users? Des this go for each user
> I
> have in SQL?
> TIA,
> Joe
>|||Thank you.
This was very helpful.
Joe
"Geoff N. Hiten" wrote:

> A CAL covers either a user or a device that connects to SQL. The gotcha i
s
> that only end users or devices count. If you have a web server or other
> device that collects end users and feeds them through a single device
> connections, then you have to license each end user, not just the single
> middle-ware device. Licensed users can have multiple connections so there
> is not any relationship between licensed users and connections. If you ha
ve
> a situation where you cannot enumerate each licensed user, such as a
> public-facing web site, then you must license SQLnon a per-processor basis
.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:DBCCB86D-7367-4AC5-9B9E-440CA72C31C1@.microsoft.com...
>
>|||Thank you,
This was very helpful
Joe
"BenUK" wrote:

> A CAL covers a connection to the DB, so whether your using a generic login
> or user specific logins each is a seperate CAL.

CAL

I know CAL stands for Client access license, does this mean if I have an
application that logs onto SQL as a generic user, is that one CAL? Do I need
a CAL for each of my application generic users? Des this go for each user I
have in SQL?
TIA,
Joe
A CAL covers a connection to the DB, so whether your using a generic login
or user specific logins each is a seperate CAL.
|||A CAL covers either a user or a device that connects to SQL. The gotcha is
that only end users or devices count. If you have a web server or other
device that collects end users and feeds them through a single device
connections, then you have to license each end user, not just the single
middle-ware device. Licensed users can have multiple connections so there
is not any relationship between licensed users and connections. If you have
a situation where you cannot enumerate each licensed user, such as a
public-facing web site, then you must license SQLnon a per-processor basis.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:DBCCB86D-7367-4AC5-9B9E-440CA72C31C1@.microsoft.com...
>I know CAL stands for Client access license, does this mean if I have an
> application that logs onto SQL as a generic user, is that one CAL? Do I
> need
> a CAL for each of my application generic users? Des this go for each user
> I
> have in SQL?
> TIA,
> Joe
>
|||Thank you.
This was very helpful.
Joe
"Geoff N. Hiten" wrote:

> A CAL covers either a user or a device that connects to SQL. The gotcha is
> that only end users or devices count. If you have a web server or other
> device that collects end users and feeds them through a single device
> connections, then you have to license each end user, not just the single
> middle-ware device. Licensed users can have multiple connections so there
> is not any relationship between licensed users and connections. If you have
> a situation where you cannot enumerate each licensed user, such as a
> public-facing web site, then you must license SQLnon a per-processor basis.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:DBCCB86D-7367-4AC5-9B9E-440CA72C31C1@.microsoft.com...
>
>
|||Thank you,
This was very helpful
Joe
"BenUK" wrote:

> A CAL covers a connection to the DB, so whether your using a generic login
> or user specific logins each is a seperate CAL.

c0000005 EXCEPTION_ACCESS_VIOLATION when querying linked server

I have SQL 2K with SP4. Oracle client is installed on the Server. I have created linked server to Oracle. I am abld to connect to Oracle Server through DTS but when I query an oracle linked server SQl Server crashes with "EXCEPTION_ACCESS_VIOLATION" error.

Info on the Server:

Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

I have the SQL dump if you need that. Please help.

Thanks

Sreejith

Hi Sreejith,

I've moving your post to the Database Engine forum. Your issue isn't a documentation issue and you'll likely get a better response in that forum.

Thanks,

Gail Erickson

SQL Server Documentation Team

|||

Whilst I cannot help a lot I can recommend that you give a little more information:

Version of Oracle (and it's host) Middleware being used (ODBC vs OLEDB driver, whose, which version) Whether Oracle is local or remote Is it any query or specific queries|||

Can you please upload the dump file?

Thanks, Ron D.

c++ lib

i am looking for c++ libs so that i may connect to sqlserver..(user does not
have client sql installed)
thanks
Hi
Look at
http://msdn.microsoft.com/library/de...asp?frame=true
Current Windows installations come with MDAC installed so you have the OLE
DB libraries.
--
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/
"Abe" <abe_icm@.verizon.net> wrote in message
news:bXAdf.2224$Pa4.1266@.trndny01...
>i am looking for c++ libs so that i may connect to sqlserver..(user does
>not have client sql installed)
> thanks
>

c++ lib

i am looking for c++ libs so that i may connect to sqlserver..(user does not
have client sql installed)
thanksHi
Look at
http://msdn.microsoft.com/library/d...asp?frame=true
Current Windows installations come with MDAC installed so you have the OLE
DB libraries.
--
--
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/
"Abe" <abe_icm@.verizon.net> wrote in message
news:bXAdf.2224$Pa4.1266@.trndny01...
>i am looking for c++ libs so that i may connect to sqlserver..(user does
>not have client sql installed)
> thanks
>

C/S and T/S using same DB simultaneously

I have a VB6 application that runs in both a client server or a terminal
services environment. Normally a customer uses one or the other. Is it
possible for a customer to install and run both of these at the same time
meaning they have the C/S connected to some users and the T/S connecting
other users but they both access one SQL server database? I had not
considered this situation before.
BruceL
Bruce,
I don't know why not. Whether the client code runs C/S or T/S is moot to
the SQL Server, since it knows very little about the client. It talks via
the communication protocols and grants rights to 'you', whoever you are.
The main issue is probably: Who are you in each of these environments? Are
you in the same security context, or not? But, however you are managing
access to the SQL Server will control who can log in and what rights are
granted.
RLF
"BruceL" <BruceL@.discussions.microsoft.com> wrote in message
news:268FAFAE-6729-4227-A95E-D60A02AEB119@.microsoft.com...
>I have a VB6 application that runs in both a client server or a terminal
> services environment. Normally a customer uses one or the other. Is it
> possible for a customer to install and run both of these at the same time
> meaning they have the C/S connected to some users and the T/S connecting
> other users but they both access one SQL server database? I had not
> considered this situation before.
> --
> BruceL
|||Thanks for the answer Russell
BruceL
"Russell Fields" wrote:

> Bruce,
> I don't know why not. Whether the client code runs C/S or T/S is moot to
> the SQL Server, since it knows very little about the client. It talks via
> the communication protocols and grants rights to 'you', whoever you are.
> The main issue is probably: Who are you in each of these environments? Are
> you in the same security context, or not? But, however you are managing
> access to the SQL Server will control who can log in and what rights are
> granted.
> RLF
> "BruceL" <BruceL@.discussions.microsoft.com> wrote in message
> news:268FAFAE-6729-4227-A95E-D60A02AEB119@.microsoft.com...
>
>

C/S and T/S using same DB simultaneously

I have a VB6 application that runs in both a client server or a terminal
services environment. Normally a customer uses one or the other. Is it
possible for a customer to install and run both of these at the same time
meaning they have the C/S connected to some users and the T/S connecting
other users but they both access one SQL server database? I had not
considered this situation before.
--
BruceLBruce,
I don't know why not. Whether the client code runs C/S or T/S is moot to
the SQL Server, since it knows very little about the client. It talks via
the communication protocols and grants rights to 'you', whoever you are.
The main issue is probably: Who are you in each of these environments? Are
you in the same security context, or not? But, however you are managing
access to the SQL Server will control who can log in and what rights are
granted.
RLF
"BruceL" <BruceL@.discussions.microsoft.com> wrote in message
news:268FAFAE-6729-4227-A95E-D60A02AEB119@.microsoft.com...
>I have a VB6 application that runs in both a client server or a terminal
> services environment. Normally a customer uses one or the other. Is it
> possible for a customer to install and run both of these at the same time
> meaning they have the C/S connected to some users and the T/S connecting
> other users but they both access one SQL server database? I had not
> considered this situation before.
> --
> BruceL|||Thanks for the answer Russell
--
BruceL
"Russell Fields" wrote:
> Bruce,
> I don't know why not. Whether the client code runs C/S or T/S is moot to
> the SQL Server, since it knows very little about the client. It talks via
> the communication protocols and grants rights to 'you', whoever you are.
> The main issue is probably: Who are you in each of these environments? Are
> you in the same security context, or not? But, however you are managing
> access to the SQL Server will control who can log in and what rights are
> granted.
> RLF
> "BruceL" <BruceL@.discussions.microsoft.com> wrote in message
> news:268FAFAE-6729-4227-A95E-D60A02AEB119@.microsoft.com...
> >I have a VB6 application that runs in both a client server or a terminal
> > services environment. Normally a customer uses one or the other. Is it
> > possible for a customer to install and run both of these at the same time
> > meaning they have the C/S connected to some users and the T/S connecting
> > other users but they both access one SQL server database? I had not
> > considered this situation before.
> > --
> > BruceL
>
>

C# - Need to find instances of SQL Server on client

How can I determine using C# which instances of SQL Server 2000,
MSDE, 2005 or 2005 Express, if any, are installed on a client
computer?
For instance, by knowing the computer's name, I could
guess at a named instance of the data provider and use
it in a connection string, assuming Windows Integrated
Security, and attempt a connection. But this is klutzy.
Is there a method of *discovery* that returns the info?
In Visual Studio 2003/2005 when attempting a new connection
in Server Explorer, an applet appears which does something
like this. Ditto in SQL Server Manager.
The intent is to use DDL, embedded in ADO.Net library
calls, to create a data schema for an application
with stored procedures. This part is easy. But first,
I need to know "who's" there.
Hi,
This enum in C# can help you.
http://blogs.msdn.com/sushilc/archive/2004/10/14/242395.aspx
Thanks
Omar
"Stratum" wrote:

> How can I determine using C# which instances of SQL Server 2000,
> MSDE, 2005 or 2005 Express, if any, are installed on a client
> computer?
> For instance, by knowing the computer's name, I could
> guess at a named instance of the data provider and use
> it in a connection string, assuming Windows Integrated
> Security, and attempt a connection. But this is klutzy.
> Is there a method of *discovery* that returns the info?
> In Visual Studio 2003/2005 when attempting a new connection
> in Server Explorer, an applet appears which does something
> like this. Ditto in SQL Server Manager.
> The intent is to use DDL, embedded in ADO.Net library
> calls, to create a data schema for an application
> with stored procedures. This part is easy. But first,
> I need to know "who's" there.
>