Is there a way to increase this value on the server or does it have to be
done at the application level? If at the app level, any suggestions as to
how.
TIA
Rob
1. Lunch EM
2. Right-click your server and select Properties.
3. Connections Tab
4. Look at your query & concurrent connection timeout settings.
Message posted via http://www.sqlmonster.com
|||Thanks, but doesn't that only apply to other servers. Or does it also apply
to clients?
"Sameer Premji via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:b80021ec3da446949b691d5fd8db0952@.SQLMonster.c om...
> 1. Lunch EM
> 2. Right-click your server and select Properties.
> 3. Connections Tab
> 4. Look at your query & concurrent connection timeout settings.
> --
> Message posted via http://www.sqlmonster.com
|||That setting applies only to the server.
You should allow a broader time-out setting at the server-level. However,
do not set it at 0 or unlimited time-out because you do not want a long-
running query or an unstable client app to bring down your server. If
someone executes 30 min query against your server, then your server will
for sure deprive other critical operations from executing and probably will
get bogged-down.
Queries are meant to execute very fast and you should make sure that they
are well tested and optimized before querying.
You should set each Client app's query time-out settings individually to a
reasonable minimum (obviously less than the max limit set at the server-
level).
For example, if you use Query Analyzer, a client app used to query SQL
server, you can set it its query time-out settings accordingly (Tools --
>Options -->Connections Tab).
If you are using a programming language, at the time of connection (via
ODBC or DSN or connection string) you can supply a parameter value for
query-time out to explicitly tell the server that I want you to allow this
specific query to run for 'n' seconds.
Hope its clear.
Message posted via http://www.sqlmonster.com
Showing posts with label level. Show all posts
Showing posts with label level. Show all posts
Friday, March 9, 2012
How can I increase the Query Timeout Value
Is there a way to increase this value on the server or does it have to be
done at the application level? If at the app level, any suggestions as to
how.
TIA
Rob1. Lunch EM
2. Right-click your server and select Properties.
3. Connections Tab
4. Look at your query & concurrent connection timeout settings.
--
Message posted via http://www.sqlmonster.com|||Thanks, but doesn't that only apply to other servers. Or does it also apply
to clients?
"Sameer Premji via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:b80021ec3da446949b691d5fd8db0952@.SQLMonster.com...
> 1. Lunch EM
> 2. Right-click your server and select Properties.
> 3. Connections Tab
> 4. Look at your query & concurrent connection timeout settings.
> --
> Message posted via http://www.sqlmonster.com|||That setting applies only to the server.
You should allow a broader time-out setting at the server-level. However,
do not set it at 0 or unlimited time-out because you do not want a long-
running query or an unstable client app to bring down your server. If
someone executes 30 min query against your server, then your server will
for sure deprive other critical operations from executing and probably will
get bogged-down.
Queries are meant to execute very fast and you should make sure that they
are well tested and optimized before querying.
You should set each Client app's query time-out settings individually to a
reasonable minimum (obviously less than the max limit set at the server-
level).
For example, if you use Query Analyzer, a client app used to query SQL
server, you can set it its query time-out settings accordingly (Tools --
>Options -->Connections Tab).
If you are using a programming language, at the time of connection (via
ODBC or DSN or connection string) you can supply a parameter value for
query-time out to explicitly tell the server that I want you to allow this
specific query to run for 'n' seconds.
Hope its clear.
--
Message posted via http://www.sqlmonster.com
done at the application level? If at the app level, any suggestions as to
how.
TIA
Rob1. Lunch EM
2. Right-click your server and select Properties.
3. Connections Tab
4. Look at your query & concurrent connection timeout settings.
--
Message posted via http://www.sqlmonster.com|||Thanks, but doesn't that only apply to other servers. Or does it also apply
to clients?
"Sameer Premji via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:b80021ec3da446949b691d5fd8db0952@.SQLMonster.com...
> 1. Lunch EM
> 2. Right-click your server and select Properties.
> 3. Connections Tab
> 4. Look at your query & concurrent connection timeout settings.
> --
> Message posted via http://www.sqlmonster.com|||That setting applies only to the server.
You should allow a broader time-out setting at the server-level. However,
do not set it at 0 or unlimited time-out because you do not want a long-
running query or an unstable client app to bring down your server. If
someone executes 30 min query against your server, then your server will
for sure deprive other critical operations from executing and probably will
get bogged-down.
Queries are meant to execute very fast and you should make sure that they
are well tested and optimized before querying.
You should set each Client app's query time-out settings individually to a
reasonable minimum (obviously less than the max limit set at the server-
level).
For example, if you use Query Analyzer, a client app used to query SQL
server, you can set it its query time-out settings accordingly (Tools --
>Options -->Connections Tab).
If you are using a programming language, at the time of connection (via
ODBC or DSN or connection string) you can supply a parameter value for
query-time out to explicitly tell the server that I want you to allow this
specific query to run for 'n' seconds.
Hope its clear.
--
Message posted via http://www.sqlmonster.com
How can I increase the Query Timeout Value
Is there a way to increase this value on the server or does it have to be
done at the application level? If at the app level, any suggestions as to
how.
TIA
Rob1. Lunch EM
2. Right-click your server and select Properties.
3. Connections Tab
4. Look at your query & concurrent connection timeout settings.
Message posted via http://www.droptable.com|||Thanks, but doesn't that only apply to other servers. Or does it also apply
to clients?
"Sameer Premji via droptable.com" <forum@.droptable.com> wrote in message
news:b80021ec3da446949b691d5fd8db0952@.SQ
droptable.com...
> 1. Lunch EM
> 2. Right-click your server and select Properties.
> 3. Connections Tab
> 4. Look at your query & concurrent connection timeout settings.
> --
> Message posted via http://www.droptable.com|||That setting applies only to the server.
You should allow a broader time-out setting at the server-level. However,
do not set it at 0 or unlimited time-out because you do not want a long-
running query or an unstable client app to bring down your server. If
someone executes 30 min query against your server, then your server will
for sure deprive other critical operations from executing and probably will
get bogged-down.
Queries are meant to execute very fast and you should make sure that they
are well tested and optimized before querying.
You should set each Client app's query time-out settings individually to a
reasonable minimum (obviously less than the max limit set at the server-
level).
For example, if you use Query Analyzer, a client app used to query SQL
server, you can set it its query time-out settings accordingly (Tools --
>Options -->Connections Tab).
If you are using a programming language, at the time of connection (via
ODBC or DSN or connection string) you can supply a parameter value for
query-time out to explicitly tell the server that I want you to allow this
specific query to run for 'n' seconds.
Hope its clear.
Message posted via http://www.droptable.com
done at the application level? If at the app level, any suggestions as to
how.
TIA
Rob1. Lunch EM
2. Right-click your server and select Properties.
3. Connections Tab
4. Look at your query & concurrent connection timeout settings.
Message posted via http://www.droptable.com|||Thanks, but doesn't that only apply to other servers. Or does it also apply
to clients?
"Sameer Premji via droptable.com" <forum@.droptable.com> wrote in message
news:b80021ec3da446949b691d5fd8db0952@.SQ
droptable.com...
> 1. Lunch EM
> 2. Right-click your server and select Properties.
> 3. Connections Tab
> 4. Look at your query & concurrent connection timeout settings.
> --
> Message posted via http://www.droptable.com|||That setting applies only to the server.
You should allow a broader time-out setting at the server-level. However,
do not set it at 0 or unlimited time-out because you do not want a long-
running query or an unstable client app to bring down your server. If
someone executes 30 min query against your server, then your server will
for sure deprive other critical operations from executing and probably will
get bogged-down.
Queries are meant to execute very fast and you should make sure that they
are well tested and optimized before querying.
You should set each Client app's query time-out settings individually to a
reasonable minimum (obviously less than the max limit set at the server-
level).
For example, if you use Query Analyzer, a client app used to query SQL
server, you can set it its query time-out settings accordingly (Tools --
>Options -->Connections Tab).
If you are using a programming language, at the time of connection (via
ODBC or DSN or connection string) you can supply a parameter value for
query-time out to explicitly tell the server that I want you to allow this
specific query to run for 'n' seconds.
Hope its clear.
Message posted via http://www.droptable.com
Wednesday, March 7, 2012
How can I hide leaf level members of a ragged dimension ?
I need to hide leaf level members of a ragged dimension. Any thoughts ? My original approach was through roles (security), but I am open to other suggestions.
Maybe I need to generalize this. Is it possible to hide lower levels of a heirarchical dimension ?
Specifically, I have our corporate organization, with the following heirarchy:
CEO-->ExecVP-->VP-->Director-->Manager-->Supervisor-->Employee.
I need to be able to hide measures associated with leaf-level employees, and also selectively at the small group (supervisor) level. But security seems to work backwards--I can hide top level aggregations, but not the lower level.
Any ideas ?
How can I hide leaf level members of a ragged dimension ?
I need to hide leaf level members of a ragged dimension. Any thoughts ? My original approach was through roles (security), but I am open to other suggestions.
Maybe I need to generalize this. Is it possible to hide lower levels of a heirarchical dimension ?
Specifically, I have our corporate organization, with the following heirarchy:
CEO-->ExecVP-->VP-->Director-->Manager-->Supervisor-->Employee.
I need to be able to hide measures associated with leaf-level employees, and also selectively at the small group (supervisor) level. But security seems to work backwards--I can hide top level aggregations, but not the lower level.
Any ideas ?
Subscribe to:
Posts (Atom)