Report Writing Access

Hello,

When we started using sql server reporting services, I played around with the report builder tool.  This tool allows users to create there own reports based off of pre existing data sets.

Jon

I would just like to point out that there's really no reason for any user to have SA access to the database.  You can create as many logins as necessary with all the proper permissions without going as far as giving SA rights.  I would highly recommend that approach.

I would just like to point out that there's really no reason for any user to have SA access to the database.  You can create as many logins as necessary with all the proper permissions without going as far as giving SA rights.  I would highly recommend that approach.

Take a look at the Security Administration document.  In section 1.A. there are directions for creating a SQL Server login that can access security but can not do any of the truly damaging things that a user with full SA rights can do, like completely dropping your database.  I would urge everyone to think very carefully about granting SA access to your database server.  Even actual administrators should only login with SA rights in case where it is really needed.  For daily work they should be using a different login which limits their ability to do damaging things.  It's even worse if you are actually giving the true SA password to multiple people.  If you do that and something bad happens, then there would be no way to figure out who actually caused the problem.  Always remember the security principle of Least Privilege.  Further, the Tessitura PCI overview has specific instructions to disable the generic SA account in SQL Server as this generic account is one of the primary security vulnerabilities.