Hi
I who'd like to know if there is a best accepted practice
that can guide me to write a regulation for limiting
Users and developers running Heavy queries on the server
during working hours."Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
Look up Query governer.
>|||There is a way to do this using the Query Governor configuration parameter.
You can specify a 'cost' limit for queries in where they won't run if the the
cost (based on execution plan) will exceed this value. You can't limit this
by user, but you can limit by connection using SET statement. All of this is
in Books online.
Colleen
"Oren" wrote:
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>|||The Query Governor option seems more like a stop-gap measure and won't
really solve the problem. If your users are running queries during business
hours to get information they need to do their jobs, limiting their ability
to run those queries might hurt more than it helps... If you have queries
that are taking a long time or using a lot of server resources, there are
several things you can do to improve performance - add resources to the
server, tune your indexes, optimize queries, optimize server
configuration... Also, can't tell from your statement, but if developers
are using your production servers for development and testing, you might
look at giving them their own SQL server...
Thanks,
Michael C., MCDBA
"Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>
Showing posts with label developers. Show all posts
Showing posts with label developers. Show all posts
Friday, March 9, 2012
limiting heavy queries
Hi
I who'd like to know if there is a best accepted practice
that can guide me to write a regulation for limiting
Users and developers running Heavy queries on the server
during working hours.
"Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
Look up Query governer.
>
|||There is a way to do this using the Query Governor configuration parameter.
You can specify a 'cost' limit for queries in where they won't run if the the
cost (based on execution plan) will exceed this value. You can't limit this
by user, but you can limit by connection using SET statement. All of this is
in Books online.
Colleen
"Oren" wrote:
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>
|||The Query Governor option seems more like a stop-gap measure and won't
really solve the problem. If your users are running queries during business
hours to get information they need to do their jobs, limiting their ability
to run those queries might hurt more than it helps... If you have queries
that are taking a long time or using a lot of server resources, there are
several things you can do to improve performance - add resources to the
server, tune your indexes, optimize queries, optimize server
configuration... Also, can't tell from your statement, but if developers
are using your production servers for development and testing, you might
look at giving them their own SQL server...
Thanks,
Michael C., MCDBA
"Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>
I who'd like to know if there is a best accepted practice
that can guide me to write a regulation for limiting
Users and developers running Heavy queries on the server
during working hours.
"Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
Look up Query governer.
>
|||There is a way to do this using the Query Governor configuration parameter.
You can specify a 'cost' limit for queries in where they won't run if the the
cost (based on execution plan) will exceed this value. You can't limit this
by user, but you can limit by connection using SET statement. All of this is
in Books online.
Colleen
"Oren" wrote:
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>
|||The Query Governor option seems more like a stop-gap measure and won't
really solve the problem. If your users are running queries during business
hours to get information they need to do their jobs, limiting their ability
to run those queries might hurt more than it helps... If you have queries
that are taking a long time or using a lot of server resources, there are
several things you can do to improve performance - add resources to the
server, tune your indexes, optimize queries, optimize server
configuration... Also, can't tell from your statement, but if developers
are using your production servers for development and testing, you might
look at giving them their own SQL server...
Thanks,
Michael C., MCDBA
"Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>
limiting heavy queries
Hi
I who'd like to know if there is a best accepted practice
that can guide me to write a regulation for limiting
Users and developers running Heavy queries on the server
during working hours."Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
Look up Query governer.
>|||There is a way to do this using the Query Governor configuration parameter.
You can specify a 'cost' limit for queries in where they won't run if the th
e
cost (based on execution plan) will exceed this value. You can't limit this
by user, but you can limit by connection using SET statement. All of this i
s
in Books online.
Colleen
"Oren" wrote:
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>|||The Query Governor option seems more like a stop-gap measure and won't
really solve the problem. If your users are running queries during business
hours to get information they need to do their jobs, limiting their ability
to run those queries might hurt more than it helps... If you have queries
that are taking a long time or using a lot of server resources, there are
several things you can do to improve performance - add resources to the
server, tune your indexes, optimize queries, optimize server
configuration... Also, can't tell from your statement, but if developers
are using your production servers for development and testing, you might
look at giving them their own SQL server...
Thanks,
Michael C., MCDBA
"Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>
I who'd like to know if there is a best accepted practice
that can guide me to write a regulation for limiting
Users and developers running Heavy queries on the server
during working hours."Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
Look up Query governer.
>|||There is a way to do this using the Query Governor configuration parameter.
You can specify a 'cost' limit for queries in where they won't run if the th
e
cost (based on execution plan) will exceed this value. You can't limit this
by user, but you can limit by connection using SET statement. All of this i
s
in Books online.
Colleen
"Oren" wrote:
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>|||The Query Governor option seems more like a stop-gap measure and won't
really solve the problem. If your users are running queries during business
hours to get information they need to do their jobs, limiting their ability
to run those queries might hurt more than it helps... If you have queries
that are taking a long time or using a lot of server resources, there are
several things you can do to improve performance - add resources to the
server, tune your indexes, optimize queries, optimize server
configuration... Also, can't tell from your statement, but if developers
are using your production servers for development and testing, you might
look at giving them their own SQL server...
Thanks,
Michael C., MCDBA
"Oren" <orenb70@.bezeqint.net> wrote in message
news:07d901c4b6e4$18097c10$a401280a@.phx.gbl...
> Hi
> I who'd like to know if there is a best accepted practice
> that can guide me to write a regulation for limiting
> Users and developers running Heavy queries on the server
> during working hours.
>
Limiting access to SQL Server 2000 for our junior developers
Hi All
I've been given a task to lockdown access to our database server to our
6 junior developers. We currently have about 25 databases on our SQL
Server. I'm trying to do the following the easiest way:
1. Create six separate logins
2. For all 25 db's only allow selects, inserts and updates for them to
all tables.
3. They must be able to create tables but not drop or truncate
anything.
4. Of course no access to the master db
5. Lock out all dangerous sp's like xp_cmdshell
I'm new to SQL permissions. What would be the easiest way to doing
this without manually adding all the permissions table level for each
login?
Thanks in advance for any help.
BillCreate a database role
grant the role data_reader permission
grant the role data_writer permission
grant the role the CREATE TABLE permission
deny the role DELETE Permission on any object
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
<bcrenshaw99@.yahoo.com> wrote in message
news:1123541934.751731.34430@.o13g2000cwo.googlegroups.com...
> Hi All
> I've been given a task to lockdown access to our database server to our
> 6 junior developers. We currently have about 25 databases on our SQL
> Server. I'm trying to do the following the easiest way:
> 1. Create six separate logins
> 2. For all 25 db's only allow selects, inserts and updates for them to
> all tables.
> 3. They must be able to create tables but not drop or truncate
> anything.
> 4. Of course no access to the master db
> 5. Lock out all dangerous sp's like xp_cmdshell
> I'm new to SQL permissions. What would be the easiest way to doing
> this without manually adding all the permissions table level for each
> login?
> Thanks in advance for any help.
> Bill
>|||Dandy
> grant the role data_writer permission
If you add him to the db_denydatawriter hi cannot be able to delete
anything
Also , don't forget to execute EXEC sp_defaultdb 'LoginName', 'database'
as well as EXEC sp_grantdbaccess 'test'
"Dandy Weyn [Dandyman]" <dandy@.dandyman.net> wrote in message
news:eAwwwNKnFHA.1948@.TK2MSFTNGP12.phx.gbl...
> Create a database role
> grant the role data_reader permission
> grant the role data_writer permission
> grant the role the CREATE TABLE permission
> deny the role DELETE Permission on any object
>
> --
> Dandy Weyn
> [MCSE-MCSA-MCDBA-MCDST-MCT]
> http://www.dandyman.net
> Check my SQL Server Resource Pages at http://www.dandyman.net/sql
> <bcrenshaw99@.yahoo.com> wrote in message
> news:1123541934.751731.34430@.o13g2000cwo.googlegroups.com...
>|||Hey Dandy
Thanks for the quick response :-)
I would assume that because database roles are created per database, I
would have do this on all 25 db's?
Dandy Weyn [Dandyman] wrote:[vbcol=seagreen]
> Create a database role
> grant the role data_reader permission
> grant the role data_writer permission
> grant the role the CREATE TABLE permission
> deny the role DELETE Permission on any object
>
> --
> Dandy Weyn
> [MCSE-MCSA-MCDBA-MCDST-MCT]
> http://www.dandyman.net
> Check my SQL Server Resource Pages at http://www.dandyman.net/sql
> <bcrenshaw99@.yahoo.com> wrote in message
> news:1123541934.751731.34430@.o13g2000cwo.googlegroups.com...|||Exactly,
However if you would add the role to the deny_data_writer as Uri specified,
the user would also not be able to insert/update which was needed in your
case.
You need to do this on every database yes.
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
<bcrenshaw99@.yahoo.com> wrote in message
news:1123565986.701157.304890@.g49g2000cwa.googlegroups.com...
> Hey Dandy
> Thanks for the quick response :-)
> I would assume that because database roles are created per database, I
> would have do this on all 25 db's?
>
>
> Dandy Weyn [Dandyman] wrote:
>|||Right, my mistake
"Dandy Weyn [Dandyman]" <dandy@.dandyman.net> wrote in message
news:OUxktvKnFHA.1468@.TK2MSFTNGP12.phx.gbl...
> Exactly,
> However if you would add the role to the deny_data_writer as Uri
> specified, the user would also not be able to insert/update which was
> needed in your case.
> You need to do this on every database yes.
>
> --
> Dandy Weyn
> [MCSE-MCSA-MCDBA-MCDST-MCT]
> http://www.dandyman.net
> Check my SQL Server Resource Pages at http://www.dandyman.net/sql
> <bcrenshaw99@.yahoo.com> wrote in message
> news:1123565986.701157.304890@.g49g2000cwa.googlegroups.com...
>
I've been given a task to lockdown access to our database server to our
6 junior developers. We currently have about 25 databases on our SQL
Server. I'm trying to do the following the easiest way:
1. Create six separate logins
2. For all 25 db's only allow selects, inserts and updates for them to
all tables.
3. They must be able to create tables but not drop or truncate
anything.
4. Of course no access to the master db
5. Lock out all dangerous sp's like xp_cmdshell
I'm new to SQL permissions. What would be the easiest way to doing
this without manually adding all the permissions table level for each
login?
Thanks in advance for any help.
BillCreate a database role
grant the role data_reader permission
grant the role data_writer permission
grant the role the CREATE TABLE permission
deny the role DELETE Permission on any object
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
<bcrenshaw99@.yahoo.com> wrote in message
news:1123541934.751731.34430@.o13g2000cwo.googlegroups.com...
> Hi All
> I've been given a task to lockdown access to our database server to our
> 6 junior developers. We currently have about 25 databases on our SQL
> Server. I'm trying to do the following the easiest way:
> 1. Create six separate logins
> 2. For all 25 db's only allow selects, inserts and updates for them to
> all tables.
> 3. They must be able to create tables but not drop or truncate
> anything.
> 4. Of course no access to the master db
> 5. Lock out all dangerous sp's like xp_cmdshell
> I'm new to SQL permissions. What would be the easiest way to doing
> this without manually adding all the permissions table level for each
> login?
> Thanks in advance for any help.
> Bill
>|||Dandy
> grant the role data_writer permission
If you add him to the db_denydatawriter hi cannot be able to delete
anything
Also , don't forget to execute EXEC sp_defaultdb 'LoginName', 'database'
as well as EXEC sp_grantdbaccess 'test'
"Dandy Weyn [Dandyman]" <dandy@.dandyman.net> wrote in message
news:eAwwwNKnFHA.1948@.TK2MSFTNGP12.phx.gbl...
> Create a database role
> grant the role data_reader permission
> grant the role data_writer permission
> grant the role the CREATE TABLE permission
> deny the role DELETE Permission on any object
>
> --
> Dandy Weyn
> [MCSE-MCSA-MCDBA-MCDST-MCT]
> http://www.dandyman.net
> Check my SQL Server Resource Pages at http://www.dandyman.net/sql
> <bcrenshaw99@.yahoo.com> wrote in message
> news:1123541934.751731.34430@.o13g2000cwo.googlegroups.com...
>|||Hey Dandy
Thanks for the quick response :-)
I would assume that because database roles are created per database, I
would have do this on all 25 db's?
Dandy Weyn [Dandyman] wrote:[vbcol=seagreen]
> Create a database role
> grant the role data_reader permission
> grant the role data_writer permission
> grant the role the CREATE TABLE permission
> deny the role DELETE Permission on any object
>
> --
> Dandy Weyn
> [MCSE-MCSA-MCDBA-MCDST-MCT]
> http://www.dandyman.net
> Check my SQL Server Resource Pages at http://www.dandyman.net/sql
> <bcrenshaw99@.yahoo.com> wrote in message
> news:1123541934.751731.34430@.o13g2000cwo.googlegroups.com...|||Exactly,
However if you would add the role to the deny_data_writer as Uri specified,
the user would also not be able to insert/update which was needed in your
case.
You need to do this on every database yes.
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
<bcrenshaw99@.yahoo.com> wrote in message
news:1123565986.701157.304890@.g49g2000cwa.googlegroups.com...
> Hey Dandy
> Thanks for the quick response :-)
> I would assume that because database roles are created per database, I
> would have do this on all 25 db's?
>
>
> Dandy Weyn [Dandyman] wrote:
>|||Right, my mistake
"Dandy Weyn [Dandyman]" <dandy@.dandyman.net> wrote in message
news:OUxktvKnFHA.1468@.TK2MSFTNGP12.phx.gbl...
> Exactly,
> However if you would add the role to the deny_data_writer as Uri
> specified, the user would also not be able to insert/update which was
> needed in your case.
> You need to do this on every database yes.
>
> --
> Dandy Weyn
> [MCSE-MCSA-MCDBA-MCDST-MCT]
> http://www.dandyman.net
> Check my SQL Server Resource Pages at http://www.dandyman.net/sql
> <bcrenshaw99@.yahoo.com> wrote in message
> news:1123565986.701157.304890@.g49g2000cwa.googlegroups.com...
>
Limiting access to Report Designer Only
Hi,
Has anyone tried to limit access to Report Designer only? We have report
developers that can't have access to Integration Services, Analysis Services,
Report Models, etc. What files or directories can we remove to limit their
access?
Thanks for your help!You do not need to run reporting services to design report with VS.NET. That
is, you can cut all your report developers' access to your reporting
services, they still can design report on their own computer, as long as
report designer is installed along with VS.NET and they have data source to
test it (of coourse they cannot test deployment).
"clutch" <clutch@.discussions.microsoft.com> wrote in message
news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
> Hi,
> Has anyone tried to limit access to Report Designer only? We have report
> developers that can't have access to Integration Services, Analysis
> Services,
> Report Models, etc. What files or directories can we remove to limit their
> access?
> Thanks for your help!|||Thanks for the reply. We've installed vs.net 2005 but don't see report
designer. How do you install it? Is there a snap-in or plug-in for Report
Designer?
Thanks!
"Norman Yuan" wrote:
> You do not need to run reporting services to design report with VS.NET. That
> is, you can cut all your report developers' access to your reporting
> services, they still can design report on their own computer, as long as
> report designer is installed along with VS.NET and they have data source to
> test it (of coourse they cannot test deployment).
> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
> > Hi,
> >
> > Has anyone tried to limit access to Report Designer only? We have report
> > developers that can't have access to Integration Services, Analysis
> > Services,
> > Report Models, etc. What files or directories can we remove to limit their
> > access?
> >
> > Thanks for your help!
>
>|||Hi Norman, we have the same issue. It seems that VS 2005 does not ship with
report designer. Can it be downloaded seperately?
"Norman Yuan" wrote:
> You do not need to run reporting services to design report with VS.NET. That
> is, you can cut all your report developers' access to your reporting
> services, they still can design report on their own computer, as long as
> report designer is installed along with VS.NET and they have data source to
> test it (of coourse they cannot test deployment).
> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
> > Hi,
> >
> > Has anyone tried to limit access to Report Designer only? We have report
> > developers that can't have access to Integration Services, Analysis
> > Services,
> > Report Models, etc. What files or directories can we remove to limit their
> > access?
> >
> > Thanks for your help!
>
>|||Install the client tools from RS 2005. It no longer requires having VS. It
comes with it's own VS that gets installed if you don't have it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ron Van Zanten" <RonVanZanten@.discussions.microsoft.com> wrote in message
news:6C6447BE-DFC7-424B-9EAF-F99436A7DD12@.microsoft.com...
> Hi Norman, we have the same issue. It seems that VS 2005 does not ship
> with
> report designer. Can it be downloaded seperately?
> "Norman Yuan" wrote:
>> You do not need to run reporting services to design report with VS.NET.
>> That
>> is, you can cut all your report developers' access to your reporting
>> services, they still can design report on their own computer, as long as
>> report designer is installed along with VS.NET and they have data source
>> to
>> test it (of coourse they cannot test deployment).
>> "clutch" <clutch@.discussions.microsoft.com> wrote in message
>> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
>> > Hi,
>> >
>> > Has anyone tried to limit access to Report Designer only? We have
>> > report
>> > developers that can't have access to Integration Services, Analysis
>> > Services,
>> > Report Models, etc. What files or directories can we remove to limit
>> > their
>> > access?
>> >
>> > Thanks for your help!
>>|||Hi Bruce,
We have installed the client tools from RS 2005 using the sql server 2005
release C2 disk. The problem is we need to be able to limit access to only
use Report Designer for certain developers. We don't want certain developers
to be able to use certain features such as SSIS, Analysis Services, Report
model designer, etc. Make sense? Is there a separate install for RS 2005
client tools?
Thanks for your help!
"Bruce L-C [MVP]" wrote:
> Install the client tools from RS 2005. It no longer requires having VS. It
> comes with it's own VS that gets installed if you don't have it.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ron Van Zanten" <RonVanZanten@.discussions.microsoft.com> wrote in message
> news:6C6447BE-DFC7-424B-9EAF-F99436A7DD12@.microsoft.com...
> > Hi Norman, we have the same issue. It seems that VS 2005 does not ship
> > with
> > report designer. Can it be downloaded seperately?
> >
> > "Norman Yuan" wrote:
> >
> >> You do not need to run reporting services to design report with VS.NET.
> >> That
> >> is, you can cut all your report developers' access to your reporting
> >> services, they still can design report on their own computer, as long as
> >> report designer is installed along with VS.NET and they have data source
> >> to
> >> test it (of coourse they cannot test deployment).
> >>
> >> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> >> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
> >> > Hi,
> >> >
> >> > Has anyone tried to limit access to Report Designer only? We have
> >> > report
> >> > developers that can't have access to Integration Services, Analysis
> >> > Services,
> >> > Report Models, etc. What files or directories can we remove to limit
> >> > their
> >> > access?
> >> >
> >> > Thanks for your help!
> >>
> >>
> >>
>
>|||What you can do is they can develop but they cannot deploy. That is easy.
Also you can manage rights to the database which would determine what they
can do. Not sure about Report model designer. I don't know much about that.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"clutch" <clutch@.discussions.microsoft.com> wrote in message
news:0E6CFB95-93CB-4537-989C-0E13C37A7228@.microsoft.com...
> Hi Bruce,
> We have installed the client tools from RS 2005 using the sql server 2005
> release C2 disk. The problem is we need to be able to limit access to only
> use Report Designer for certain developers. We don't want certain
> developers
> to be able to use certain features such as SSIS, Analysis Services, Report
> model designer, etc. Make sense? Is there a separate install for RS 2005
> client tools?
> Thanks for your help!
> "Bruce L-C [MVP]" wrote:
>> Install the client tools from RS 2005. It no longer requires having VS.
>> It
>> comes with it's own VS that gets installed if you don't have it.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ron Van Zanten" <RonVanZanten@.discussions.microsoft.com> wrote in
>> message
>> news:6C6447BE-DFC7-424B-9EAF-F99436A7DD12@.microsoft.com...
>> > Hi Norman, we have the same issue. It seems that VS 2005 does not ship
>> > with
>> > report designer. Can it be downloaded seperately?
>> >
>> > "Norman Yuan" wrote:
>> >
>> >> You do not need to run reporting services to design report with
>> >> VS.NET.
>> >> That
>> >> is, you can cut all your report developers' access to your reporting
>> >> services, they still can design report on their own computer, as long
>> >> as
>> >> report designer is installed along with VS.NET and they have data
>> >> source
>> >> to
>> >> test it (of coourse they cannot test deployment).
>> >>
>> >> "clutch" <clutch@.discussions.microsoft.com> wrote in message
>> >> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
>> >> > Hi,
>> >> >
>> >> > Has anyone tried to limit access to Report Designer only? We have
>> >> > report
>> >> > developers that can't have access to Integration Services, Analysis
>> >> > Services,
>> >> > Report Models, etc. What files or directories can we remove to limit
>> >> > their
>> >> > access?
>> >> >
>> >> > Thanks for your help!
>> >>
>> >>
>> >>
>>
Has anyone tried to limit access to Report Designer only? We have report
developers that can't have access to Integration Services, Analysis Services,
Report Models, etc. What files or directories can we remove to limit their
access?
Thanks for your help!You do not need to run reporting services to design report with VS.NET. That
is, you can cut all your report developers' access to your reporting
services, they still can design report on their own computer, as long as
report designer is installed along with VS.NET and they have data source to
test it (of coourse they cannot test deployment).
"clutch" <clutch@.discussions.microsoft.com> wrote in message
news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
> Hi,
> Has anyone tried to limit access to Report Designer only? We have report
> developers that can't have access to Integration Services, Analysis
> Services,
> Report Models, etc. What files or directories can we remove to limit their
> access?
> Thanks for your help!|||Thanks for the reply. We've installed vs.net 2005 but don't see report
designer. How do you install it? Is there a snap-in or plug-in for Report
Designer?
Thanks!
"Norman Yuan" wrote:
> You do not need to run reporting services to design report with VS.NET. That
> is, you can cut all your report developers' access to your reporting
> services, they still can design report on their own computer, as long as
> report designer is installed along with VS.NET and they have data source to
> test it (of coourse they cannot test deployment).
> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
> > Hi,
> >
> > Has anyone tried to limit access to Report Designer only? We have report
> > developers that can't have access to Integration Services, Analysis
> > Services,
> > Report Models, etc. What files or directories can we remove to limit their
> > access?
> >
> > Thanks for your help!
>
>|||Hi Norman, we have the same issue. It seems that VS 2005 does not ship with
report designer. Can it be downloaded seperately?
"Norman Yuan" wrote:
> You do not need to run reporting services to design report with VS.NET. That
> is, you can cut all your report developers' access to your reporting
> services, they still can design report on their own computer, as long as
> report designer is installed along with VS.NET and they have data source to
> test it (of coourse they cannot test deployment).
> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
> > Hi,
> >
> > Has anyone tried to limit access to Report Designer only? We have report
> > developers that can't have access to Integration Services, Analysis
> > Services,
> > Report Models, etc. What files or directories can we remove to limit their
> > access?
> >
> > Thanks for your help!
>
>|||Install the client tools from RS 2005. It no longer requires having VS. It
comes with it's own VS that gets installed if you don't have it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ron Van Zanten" <RonVanZanten@.discussions.microsoft.com> wrote in message
news:6C6447BE-DFC7-424B-9EAF-F99436A7DD12@.microsoft.com...
> Hi Norman, we have the same issue. It seems that VS 2005 does not ship
> with
> report designer. Can it be downloaded seperately?
> "Norman Yuan" wrote:
>> You do not need to run reporting services to design report with VS.NET.
>> That
>> is, you can cut all your report developers' access to your reporting
>> services, they still can design report on their own computer, as long as
>> report designer is installed along with VS.NET and they have data source
>> to
>> test it (of coourse they cannot test deployment).
>> "clutch" <clutch@.discussions.microsoft.com> wrote in message
>> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
>> > Hi,
>> >
>> > Has anyone tried to limit access to Report Designer only? We have
>> > report
>> > developers that can't have access to Integration Services, Analysis
>> > Services,
>> > Report Models, etc. What files or directories can we remove to limit
>> > their
>> > access?
>> >
>> > Thanks for your help!
>>|||Hi Bruce,
We have installed the client tools from RS 2005 using the sql server 2005
release C2 disk. The problem is we need to be able to limit access to only
use Report Designer for certain developers. We don't want certain developers
to be able to use certain features such as SSIS, Analysis Services, Report
model designer, etc. Make sense? Is there a separate install for RS 2005
client tools?
Thanks for your help!
"Bruce L-C [MVP]" wrote:
> Install the client tools from RS 2005. It no longer requires having VS. It
> comes with it's own VS that gets installed if you don't have it.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ron Van Zanten" <RonVanZanten@.discussions.microsoft.com> wrote in message
> news:6C6447BE-DFC7-424B-9EAF-F99436A7DD12@.microsoft.com...
> > Hi Norman, we have the same issue. It seems that VS 2005 does not ship
> > with
> > report designer. Can it be downloaded seperately?
> >
> > "Norman Yuan" wrote:
> >
> >> You do not need to run reporting services to design report with VS.NET.
> >> That
> >> is, you can cut all your report developers' access to your reporting
> >> services, they still can design report on their own computer, as long as
> >> report designer is installed along with VS.NET and they have data source
> >> to
> >> test it (of coourse they cannot test deployment).
> >>
> >> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> >> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
> >> > Hi,
> >> >
> >> > Has anyone tried to limit access to Report Designer only? We have
> >> > report
> >> > developers that can't have access to Integration Services, Analysis
> >> > Services,
> >> > Report Models, etc. What files or directories can we remove to limit
> >> > their
> >> > access?
> >> >
> >> > Thanks for your help!
> >>
> >>
> >>
>
>|||What you can do is they can develop but they cannot deploy. That is easy.
Also you can manage rights to the database which would determine what they
can do. Not sure about Report model designer. I don't know much about that.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"clutch" <clutch@.discussions.microsoft.com> wrote in message
news:0E6CFB95-93CB-4537-989C-0E13C37A7228@.microsoft.com...
> Hi Bruce,
> We have installed the client tools from RS 2005 using the sql server 2005
> release C2 disk. The problem is we need to be able to limit access to only
> use Report Designer for certain developers. We don't want certain
> developers
> to be able to use certain features such as SSIS, Analysis Services, Report
> model designer, etc. Make sense? Is there a separate install for RS 2005
> client tools?
> Thanks for your help!
> "Bruce L-C [MVP]" wrote:
>> Install the client tools from RS 2005. It no longer requires having VS.
>> It
>> comes with it's own VS that gets installed if you don't have it.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ron Van Zanten" <RonVanZanten@.discussions.microsoft.com> wrote in
>> message
>> news:6C6447BE-DFC7-424B-9EAF-F99436A7DD12@.microsoft.com...
>> > Hi Norman, we have the same issue. It seems that VS 2005 does not ship
>> > with
>> > report designer. Can it be downloaded seperately?
>> >
>> > "Norman Yuan" wrote:
>> >
>> >> You do not need to run reporting services to design report with
>> >> VS.NET.
>> >> That
>> >> is, you can cut all your report developers' access to your reporting
>> >> services, they still can design report on their own computer, as long
>> >> as
>> >> report designer is installed along with VS.NET and they have data
>> >> source
>> >> to
>> >> test it (of coourse they cannot test deployment).
>> >>
>> >> "clutch" <clutch@.discussions.microsoft.com> wrote in message
>> >> news:C5788379-967C-4EC3-B561-57E19C898AC1@.microsoft.com...
>> >> > Hi,
>> >> >
>> >> > Has anyone tried to limit access to Report Designer only? We have
>> >> > report
>> >> > developers that can't have access to Integration Services, Analysis
>> >> > Services,
>> >> > Report Models, etc. What files or directories can we remove to limit
>> >> > their
>> >> > access?
>> >> >
>> >> > Thanks for your help!
>> >>
>> >>
>> >>
>>
Wednesday, March 7, 2012
limited permissions on test server for developers
I want to give developers limited permissions on a test sql server 2005
database. Basically they should be able to add columns to a table or
modify a columns datatype.
Create table and view definition have been granted to the developer
accounts (along with insert/update/delete), but they receive the
following error when trying to modify a table schema:
table dbo.ppir is set to read only, user doesn't have enough rights on
this table.
I am fairly new to sql server, but I did do some searching to find an
answer. I would prefer not to give them db owner permissions if
possible.
Thanks,
Andyandy wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
>
You could add the accounts to the "db_ddladmin" role on the database.
Regards,
lucm|||Hi Andy
They will need ALTER TABLE permission on the given table. See ALTER TABLE in
books online for more.
John
"andy" wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
> Create table and view definition have been granted to the developer
> accounts (along with insert/update/delete), but they receive the
> following error when trying to modify a table schema:
> table dbo.ppir is set to read only, user doesn't have enough rights on
> this table.
> I am fairly new to sql server, but I did do some searching to find an
> answer. I would prefer not to give them db owner permissions if
> possible.
> Thanks,
> Andy
>|||This worked. Thanks for the help
Andy
On Nov 16, 12:45 pm, "lucm" <l...@.iqato.com> wrote:
> andy wrote:
> > I want to give developers limited permissions on a test sql server 2005
> > database. Basically they should be able to add columns to a table or
> > modify a columns datatype.You could add the accounts to the "db_ddladmin" role on the database.
> Regards,
> lucm
database. Basically they should be able to add columns to a table or
modify a columns datatype.
Create table and view definition have been granted to the developer
accounts (along with insert/update/delete), but they receive the
following error when trying to modify a table schema:
table dbo.ppir is set to read only, user doesn't have enough rights on
this table.
I am fairly new to sql server, but I did do some searching to find an
answer. I would prefer not to give them db owner permissions if
possible.
Thanks,
Andyandy wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
>
You could add the accounts to the "db_ddladmin" role on the database.
Regards,
lucm|||Hi Andy
They will need ALTER TABLE permission on the given table. See ALTER TABLE in
books online for more.
John
"andy" wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
> Create table and view definition have been granted to the developer
> accounts (along with insert/update/delete), but they receive the
> following error when trying to modify a table schema:
> table dbo.ppir is set to read only, user doesn't have enough rights on
> this table.
> I am fairly new to sql server, but I did do some searching to find an
> answer. I would prefer not to give them db owner permissions if
> possible.
> Thanks,
> Andy
>|||This worked. Thanks for the help
Andy
On Nov 16, 12:45 pm, "lucm" <l...@.iqato.com> wrote:
> andy wrote:
> > I want to give developers limited permissions on a test sql server 2005
> > database. Basically they should be able to add columns to a table or
> > modify a columns datatype.You could add the accounts to the "db_ddladmin" role on the database.
> Regards,
> lucm
limited permissions on test server for developers
I want to give developers limited permissions on a test sql server 2005
database. Basically they should be able to add columns to a table or
modify a columns datatype.
Create table and view definition have been granted to the developer
accounts (along with insert/update/delete), but they receive the
following error when trying to modify a table schema:
table dbo.ppir is set to read only, user doesn't have enough rights on
this table.
I am fairly new to sql server, but I did do some searching to find an
answer. I would prefer not to give them db owner permissions if
possible.
Thanks,
Andy
andy wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
>
You could add the accounts to the "db_ddladmin" role on the database.
Regards,
lucm
|||Hi Andy
They will need ALTER TABLE permission on the given table. See ALTER TABLE in
books online for more.
John
"andy" wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
> Create table and view definition have been granted to the developer
> accounts (along with insert/update/delete), but they receive the
> following error when trying to modify a table schema:
> table dbo.ppir is set to read only, user doesn't have enough rights on
> this table.
> I am fairly new to sql server, but I did do some searching to find an
> answer. I would prefer not to give them db owner permissions if
> possible.
> Thanks,
> Andy
>
|||This worked. Thanks for the help
Andy
On Nov 16, 12:45 pm, "lucm" <l...@.iqato.com> wrote:
> andy wrote:
> Regards,
> lucm
database. Basically they should be able to add columns to a table or
modify a columns datatype.
Create table and view definition have been granted to the developer
accounts (along with insert/update/delete), but they receive the
following error when trying to modify a table schema:
table dbo.ppir is set to read only, user doesn't have enough rights on
this table.
I am fairly new to sql server, but I did do some searching to find an
answer. I would prefer not to give them db owner permissions if
possible.
Thanks,
Andy
andy wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
>
You could add the accounts to the "db_ddladmin" role on the database.
Regards,
lucm
|||Hi Andy
They will need ALTER TABLE permission on the given table. See ALTER TABLE in
books online for more.
John
"andy" wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
> Create table and view definition have been granted to the developer
> accounts (along with insert/update/delete), but they receive the
> following error when trying to modify a table schema:
> table dbo.ppir is set to read only, user doesn't have enough rights on
> this table.
> I am fairly new to sql server, but I did do some searching to find an
> answer. I would prefer not to give them db owner permissions if
> possible.
> Thanks,
> Andy
>
|||This worked. Thanks for the help
Andy
On Nov 16, 12:45 pm, "lucm" <l...@.iqato.com> wrote:
> andy wrote:
> Regards,
> lucm
limited permissions on test server for developers
I want to give developers limited permissions on a test sql server 2005
database. Basically they should be able to add columns to a table or
modify a columns datatype.
Create table and view definition have been granted to the developer
accounts (along with insert/update/delete), but they receive the
following error when trying to modify a table schema:
table dbo.ppir is set to read only, user doesn't have enough rights on
this table.
I am fairly new to sql server, but I did do some searching to find an
answer. I would prefer not to give them db owner permissions if
possible.
Thanks,
Andyandy wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
>
You could add the accounts to the "db_ddladmin" role on the database.
Regards,
lucm|||Hi Andy
They will need ALTER TABLE permission on the given table. See ALTER TABLE in
books online for more.
John
"andy" wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
> Create table and view definition have been granted to the developer
> accounts (along with insert/update/delete), but they receive the
> following error when trying to modify a table schema:
> table dbo.ppir is set to read only, user doesn't have enough rights on
> this table.
> I am fairly new to sql server, but I did do some searching to find an
> answer. I would prefer not to give them db owner permissions if
> possible.
> Thanks,
> Andy
>|||This worked. Thanks for the help
Andy
On Nov 16, 12:45 pm, "lucm" <l...@.iqato.com> wrote:
> andy wrote:
> Regards,
> lucm
database. Basically they should be able to add columns to a table or
modify a columns datatype.
Create table and view definition have been granted to the developer
accounts (along with insert/update/delete), but they receive the
following error when trying to modify a table schema:
table dbo.ppir is set to read only, user doesn't have enough rights on
this table.
I am fairly new to sql server, but I did do some searching to find an
answer. I would prefer not to give them db owner permissions if
possible.
Thanks,
Andyandy wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
>
You could add the accounts to the "db_ddladmin" role on the database.
Regards,
lucm|||Hi Andy
They will need ALTER TABLE permission on the given table. See ALTER TABLE in
books online for more.
John
"andy" wrote:
> I want to give developers limited permissions on a test sql server 2005
> database. Basically they should be able to add columns to a table or
> modify a columns datatype.
> Create table and view definition have been granted to the developer
> accounts (along with insert/update/delete), but they receive the
> following error when trying to modify a table schema:
> table dbo.ppir is set to read only, user doesn't have enough rights on
> this table.
> I am fairly new to sql server, but I did do some searching to find an
> answer. I would prefer not to give them db owner permissions if
> possible.
> Thanks,
> Andy
>|||This worked. Thanks for the help
Andy
On Nov 16, 12:45 pm, "lucm" <l...@.iqato.com> wrote:
> andy wrote:
> Regards,
> lucm
Subscribe to:
Posts (Atom)