We are considering turning off parallelism on our server. I've read a
few articles that also talk about limiting parallelism to a certain
number of processors instead of turning it off completely. They say
that this requirement is rare but don't describe situations where it
might be useful.
Does anyone have any information about scenarios where limiting
parallelism to a certain number of processors could be useful?
ThanksIt is very often more efficient to set sql server to use only one cpu for
each worker thread. Testing will be what determines whether it is effective
on your data with your code.
--
TheSQLGuru
President
Indicium Resources, Inc.
<pshroads@.gmail.com> wrote in message
news:1177369370.045211.148410@.l77g2000hsb.googlegroups.com...
> We are considering turning off parallelism on our server. I've read a
> few articles that also talk about limiting parallelism to a certain
> number of processors instead of turning it off completely. They say
> that this requirement is rare but don't describe situations where it
> might be useful.
> Does anyone have any information about scenarios where limiting
> parallelism to a certain number of processors could be useful?
> Thanks
>|||On 24.04.2007 01:02, pshroads@.gmail.com wrote:
> We are considering turning off parallelism on our server. I've read a
> few articles that also talk about limiting parallelism to a certain
> number of processors instead of turning it off completely. They say
> that this requirement is rare but don't describe situations where it
> might be useful.
> Does anyone have any information about scenarios where limiting
> parallelism to a certain number of processors could be useful?
Did you see these?
http://blogs.msdn.com/sqltips/archive/2005/09/14/466387.aspx
http://blogs.msdn.com/sqlcat/archive/2005/11/30/498415.aspx
robert|||Hi,
Are you using Hyperthreaded CPU's? If you are look at these threads in this
NG.
Dated April 12th - Option (MAXDOP 1)
Dated April 19th - Hyperthreaded CPU's
Chris
<pshroads@.gmail.com> wrote in message
news:1177369370.045211.148410@.l77g2000hsb.googlegroups.com...
> We are considering turning off parallelism on our server. I've read a
> few articles that also talk about limiting parallelism to a certain
> number of processors instead of turning it off completely. They say
> that this requirement is rare but don't describe situations where it
> might be useful.
> Does anyone have any information about scenarios where limiting
> parallelism to a certain number of processors could be useful?
> Thanks
>
Showing posts with label certain. Show all posts
Showing posts with label certain. Show all posts
Friday, March 9, 2012
Limiting access to certain DB's
I need to install EM and QA on my users machines, is there a way to limit their access to only certain databases in EM and QA? I only want them to see say database X in both EM and QA, and also limit what they can do it in QA(like Select, run make table/
update queries)? What would be the best way to manage this? How can I force a user to logon with a cetain Login account in EM and QA? Thanks for your help!
Easiest is to use Windows logins in SQL Server and then work with the regular security system inside SQL
Server (logins, users, roles and permissions).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mikeb" <anonymous@.discussions.microsoft.com> wrote in message
news:F2CE354A-60B3-4914-B572-98F3DDE9D842@.microsoft.com...
> I need to install EM and QA on my users machines, is there a way to limit their access to only certain
databases in EM and QA? I only want them to see say database X in both EM and QA, and also limit what they
can do it in QA(like Select, run make table/update queries)? What would be the best way to manage this? How
can I force a user to logon with a cetain Login account in EM and QA? Thanks for your help!
|||mikeb wrote:
> I need to install EM and QA on my users machines, is there a way to
> limit their access to only certain databases in EM and QA? I only
> want them to see say database X in both EM and QA, and also limit
> what they can do it in QA(like Select, run make table/update
> queries)? What would be the best way to manage this? How can I
> force a user to logon with a cetain Login account in EM and QA?
> Thanks for your help!
What Tibor said is the best answer. In addition, you may want to have a look
at our OmniView product. It is a query tool designed for users who aren't
the DBA type. It integrates their login permissions, so data editing
controls are disabled if they don't have the appropriate Update, Insert, or
Delete permissions. If they don't have any access to particular databases,
or tables, they aren't displayed at all in the various lists.
It does not perform the schema modification functions of EM, but it is a
viable query tool to serve the purpose of QA.
Steve Troxell
Krell Software - Database Tools for MS SQL Server
http://www.krell-software.com
update queries)? What would be the best way to manage this? How can I force a user to logon with a cetain Login account in EM and QA? Thanks for your help!
Easiest is to use Windows logins in SQL Server and then work with the regular security system inside SQL
Server (logins, users, roles and permissions).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mikeb" <anonymous@.discussions.microsoft.com> wrote in message
news:F2CE354A-60B3-4914-B572-98F3DDE9D842@.microsoft.com...
> I need to install EM and QA on my users machines, is there a way to limit their access to only certain
databases in EM and QA? I only want them to see say database X in both EM and QA, and also limit what they
can do it in QA(like Select, run make table/update queries)? What would be the best way to manage this? How
can I force a user to logon with a cetain Login account in EM and QA? Thanks for your help!
|||mikeb wrote:
> I need to install EM and QA on my users machines, is there a way to
> limit their access to only certain databases in EM and QA? I only
> want them to see say database X in both EM and QA, and also limit
> what they can do it in QA(like Select, run make table/update
> queries)? What would be the best way to manage this? How can I
> force a user to logon with a cetain Login account in EM and QA?
> Thanks for your help!
What Tibor said is the best answer. In addition, you may want to have a look
at our OmniView product. It is a query tool designed for users who aren't
the DBA type. It integrates their login permissions, so data editing
controls are disabled if they don't have the appropriate Update, Insert, or
Delete permissions. If they don't have any access to particular databases,
or tables, they aren't displayed at all in the various lists.
It does not perform the schema modification functions of EM, but it is a
viable query tool to serve the purpose of QA.
Steve Troxell
Krell Software - Database Tools for MS SQL Server
http://www.krell-software.com
Friday, February 24, 2012
limit years from cube?
I have 10 years in my time dimension but I only want to display 5 of those
years in certain cube. How would I limit the number of years from a
dimension?Easiest way would be to use a standard SQL view for your dim in AS.
Ray Higdon MCSE, MCDBA, CCNA
--
"JJ" <swrothfuss@.hotmail.com> wrote in message
news:%23$avJRhBEHA.1544@.TK2MSFTNGP09.phx.gbl...
> I have 10 years in my time dimension but I only want to display 5 of those
> years in certain cube. How would I limit the number of years from a
> dimension?
>
years in certain cube. How would I limit the number of years from a
dimension?Easiest way would be to use a standard SQL view for your dim in AS.
Ray Higdon MCSE, MCDBA, CCNA
--
"JJ" <swrothfuss@.hotmail.com> wrote in message
news:%23$avJRhBEHA.1544@.TK2MSFTNGP09.phx.gbl...
> I have 10 years in my time dimension but I only want to display 5 of those
> years in certain cube. How would I limit the number of years from a
> dimension?
>
limit user account to a table or database or view
Hello I think i have read in other posts that there is not way in
sql200 to limit access to a view to a certain user. What work arounds
are there for this, Can I schedule a dts export to a different database
or table and the assign rights only to data database or table? Can
anyone give some steps to create a secure login to a single sql view?
thanksIn SQL Server 2000, a user in a database does not have any access to an
object (table, view, proc, etc.) unless that user 1) owns it, 2) they
have been granted explicit permissions to it or 3) they have implicit
permissions to it via their role membership within the DB.
If you want a single DB user to only have access to a single view in a
database and no other database objects in that database, you just grant
them the appropriate permissions to that view with the GRANT statement
(presumably we're talking about SELECT permissions here), make sure the
"public" role in the database has no explicit permissions to anything
(which, by default, it doesn't) and make sure the user is not a member
of any other role in the DB (every user in a database is a member of
"public", you can't change that). This will guarantee that the only
object the user can interact with in the DB is that view.
Is that your goal? (Also, are you talking about SQL 2000 or SQL 2005?)
*mike hodgson*
blog: http://sqlnerd.blogspot.com
joe wrote:
>Hello I think i have read in other posts that there is not way in
>sql200 to limit access to a view to a certain user. What work arounds
>are there for this, Can I schedule a dts export to a different database
>or table and the assign rights only to data database or table? Can
>anyone give some steps to create a secure login to a single sql view?
>thanks
>
>|||Hi,
Nope its not possible to in SQL 2000 but you can restrict your users to
access it using sp_revokedbaccess , offcourse they can see that this db
exists in dblist but they wont able to access it . this is a fixed in SQL
2005.
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"joe" wrote:
> Hello I think i have read in other posts that there is not way in
> sql200 to limit access to a view to a certain user. What work arounds
> are there for this, Can I schedule a dts export to a different database
> or table and the assign rights only to data database or table? Can
> anyone give some steps to create a secure login to a single sql view?
> thanks
>|||I think we need some clarification from the OP as to what he's trying to
achieve. Joe, what exactly are you trying to do? Are you trying to
*hide* a database from various SQL server logins in SQL Enterprise
Manager (SQL 2000) on a particular server (Andy's reply)? Or are you
trying to make sure a particular database user *can only access a
single*, specific object within the database (my original reply)? Or
are you trying to make sure that a particular database user *cannot*
access a particular database object within the database (this can be
done with the DENY statement)?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Andy Davis wrote:
>Hi,
>Nope its not possible to in SQL 2000 but you can restrict your users to
>access it using sp_revokedbaccess , offcourse they can see that this db
>exists in dblist but they wont able to access it . this is a fixed in SQL
>2005.
>Regards
>|||Hi,
true we need to wait for his response.
:-)
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Mike Hodgson" wrote:
> I think we need some clarification from the OP as to what he's trying to
> achieve. Joe, what exactly are you trying to do? Are you trying to
> *hide* a database from various SQL server logins in SQL Enterprise
> Manager (SQL 2000) on a particular server (Andy's reply)? Or are you
> trying to make sure a particular database user *can only access a
> single*, specific object within the database (my original reply)? Or
> are you trying to make sure that a particular database user *cannot*
> access a particular database object within the database (this can be
> done with the DENY statement)?
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Andy Davis wrote:
>
>|||I know this question is old and that comments are not likely to be helpful,
but my interpretation of the question was that Joe wants a particular user
to be able to access a specific view but all other users should not have
access to the view. My understanding of the requirement is that the
requirement does not prevent a single user from having access to anything
else.
It is certainly best to get the requirements clarified before attempting to
suggest solutions.
I did not quote Mike's comment because it is posted using HTML format and
when I replied to it Outlook Express did not provide for it the quotation
symbols at the left of quoted text.
sql200 to limit access to a view to a certain user. What work arounds
are there for this, Can I schedule a dts export to a different database
or table and the assign rights only to data database or table? Can
anyone give some steps to create a secure login to a single sql view?
thanksIn SQL Server 2000, a user in a database does not have any access to an
object (table, view, proc, etc.) unless that user 1) owns it, 2) they
have been granted explicit permissions to it or 3) they have implicit
permissions to it via their role membership within the DB.
If you want a single DB user to only have access to a single view in a
database and no other database objects in that database, you just grant
them the appropriate permissions to that view with the GRANT statement
(presumably we're talking about SELECT permissions here), make sure the
"public" role in the database has no explicit permissions to anything
(which, by default, it doesn't) and make sure the user is not a member
of any other role in the DB (every user in a database is a member of
"public", you can't change that). This will guarantee that the only
object the user can interact with in the DB is that view.
Is that your goal? (Also, are you talking about SQL 2000 or SQL 2005?)
*mike hodgson*
blog: http://sqlnerd.blogspot.com
joe wrote:
>Hello I think i have read in other posts that there is not way in
>sql200 to limit access to a view to a certain user. What work arounds
>are there for this, Can I schedule a dts export to a different database
>or table and the assign rights only to data database or table? Can
>anyone give some steps to create a secure login to a single sql view?
>thanks
>
>|||Hi,
Nope its not possible to in SQL 2000 but you can restrict your users to
access it using sp_revokedbaccess , offcourse they can see that this db
exists in dblist but they wont able to access it . this is a fixed in SQL
2005.
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"joe" wrote:
> Hello I think i have read in other posts that there is not way in
> sql200 to limit access to a view to a certain user. What work arounds
> are there for this, Can I schedule a dts export to a different database
> or table and the assign rights only to data database or table? Can
> anyone give some steps to create a secure login to a single sql view?
> thanks
>|||I think we need some clarification from the OP as to what he's trying to
achieve. Joe, what exactly are you trying to do? Are you trying to
*hide* a database from various SQL server logins in SQL Enterprise
Manager (SQL 2000) on a particular server (Andy's reply)? Or are you
trying to make sure a particular database user *can only access a
single*, specific object within the database (my original reply)? Or
are you trying to make sure that a particular database user *cannot*
access a particular database object within the database (this can be
done with the DENY statement)?
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Andy Davis wrote:
>Hi,
>Nope its not possible to in SQL 2000 but you can restrict your users to
>access it using sp_revokedbaccess , offcourse they can see that this db
>exists in dblist but they wont able to access it . this is a fixed in SQL
>2005.
>Regards
>|||Hi,
true we need to wait for his response.
:-)
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Mike Hodgson" wrote:
> I think we need some clarification from the OP as to what he's trying to
> achieve. Joe, what exactly are you trying to do? Are you trying to
> *hide* a database from various SQL server logins in SQL Enterprise
> Manager (SQL 2000) on a particular server (Andy's reply)? Or are you
> trying to make sure a particular database user *can only access a
> single*, specific object within the database (my original reply)? Or
> are you trying to make sure that a particular database user *cannot*
> access a particular database object within the database (this can be
> done with the DENY statement)?
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Andy Davis wrote:
>
>|||I know this question is old and that comments are not likely to be helpful,
but my interpretation of the question was that Joe wants a particular user
to be able to access a specific view but all other users should not have
access to the view. My understanding of the requirement is that the
requirement does not prevent a single user from having access to anything
else.
It is certainly best to get the requirements clarified before attempting to
suggest solutions.
I did not quote Mike's comment because it is posted using HTML format and
when I replied to it Outlook Express did not provide for it the quotation
symbols at the left of quoted text.
Subscribe to:
Posts (Atom)