Defining custom Roles with limited access to SQL Objects

Hi!

I'm assisting in the creation of a development enviroment with SQL Server 2005, and I need to assign some custom roles, in particular, a Stored Developer Role should be able to create, modify and execute Stored Procedures but they should not be able to alter tables or views, but should be able to retrieve/insert data from those tables.

I've tried with the default roles in 2005 to no avail.

Is there a relatively easy way to accomplish this with a database alredy populated with objects of both kinds? (SP's and Tables / Views)

Thanks!

You should create your own role and assign the required permissions to it. See CREATE ROLE for information on how to create a role.

Thanks
Laurentiu

Defining custom column groups on a matrix report in report builder

I have table called Buildings which has market and sq. ft information.
I want to create a matrix report that has the market as the row group and
sq. ft ranges as the column group and shows the # of buildings in each
market that fall in the sq. ft ranges.
Sq. ft ranges are 0-5000, 5001-10000 etc...
My questions is a) is this something that can be done using report builder
b) how do i define the sq. ft ranges
c) how do I find the count of buildings whose sq. footage falls within the
range.
ThanksOn Nov 14, 1:18 pm, "shikarishambu" <shikarishamb...@.hotmail.com>
wrote:
> I have table called Buildings which has market and sq. ft information.
> I want to create a matrix report that has the market as the row group and
> sq. ft ranges as the column group and shows the # of buildings in each
> market that fall in the sq. ft ranges.
> Sq. ft ranges are 0-5000, 5001-10000 etc...
> My questions is a) is this something that can be done using report builder
> b) how do i define the sq. ft ranges
> c) how do I find the count of buildings whose sq. footage falls within the
> range.
> Thanks
A) Yes
B) In your Datasets window, right-click on the name of the dataset and
Add a new field. Call it "Sq Foot Range" and make it a calculated
field. Use an expression like
= Fields!SqFoot.Value - Fields!SqFoot.Value Mod 5000
Since you are shifting your range to include the evenly divided number
in the lower group, you really want
= CStr( ( (X-1) - (X-1) Mod 5000 ) + 1 ) & " to " & CStr( ( (X-1) -
(X-1) Mod 5000 ) + 5000 )
C) Create a Matrix with a Market in the Row Group, Sq Foot Range in
the Column Group, and Count( Fields!SqFoot.Value ) in the Details.
Hope that helps.
-- Scott

default versus named instance with custom app

Are there some general recommendations/guidelines/best practices for choosing to run your custom application against a default or named instance of SQL Server?

We have an application, which in it's stand-alone/local configuration, installs an MSDE default instance if it does not already exist, and runs against this instance. In addition, regardless of whether or not it installs the default instance, it expects to run against the default instance.

We are looking into migrating to SQL Server 2005 Express (Compact almost fits our needs, but not quite), and would like to pay more attention to the best solution regarding the use of instances, default versus named.

Thanks

hi,

1TechZ wrote:

Are there some general recommendations/guidelines/best practices for choosing to run your custom application against a default or named instance of SQL Server?

the "general" recomendation is to use a "standard" named instance named SQLExpress idf you do not need particular custom settings..

We have an application, which in it's stand-alone/local configuration, installs an MSDE default instance if it does not already exist, and runs against this instance. In addition, regardless of whether or not it installs the default instance, it expects to run against the default instance.

this is not a "best practice" behaviour.. users should be able to identify the instance the application should run against..

regards

|||

As Andrea indicated, it will be 'best' you your application has its own instance. That way you will have complete control over the security.

If you use the default instance, or the SQLExpress instance, since the user may have administrator priviledges, he/she may be able to access your database, even altering schema and/or code. Not particularly something you want to have to support.