Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Data Warehousing / August 2006

Tip: Looking for answers? Try searching our database.

Reporting Tool Information

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
faceman28208@yahoo.com - 08 Aug 2006 15:55 GMT
I am investigating whether there might be some commerical package that
might meet this kind of requirements.

I need a reporting system that will allow users (e.g. programmers for
the users) to write their own reports. However, I need to be able to
limit access to particular records within the database.

I have table used to run the business that contain information related
to many different users. I want users to be ablet to run queries
against these tables (abeit indirectly) and have automatic filters
applied that limit the records they can select.

In other words having
"WHERE USERID="12324"  automatically placed on any query the user runs
(presumably indirectly).
Jeje - 13 Aug 2006 15:10 GMT
does your users will create reports themself or only the developpers will
create reports and the users will use these reports?

for the second case, near any reporting tool do the job, its the role of the
developper to use correctly the user login into the SQL queries.

for the first case, Microsoft Report Builder, Business Objects, Cognos
ReportNet, can allow your users to create reports and apply security
automatically.
I think there is more tools on the market.
also, you can secure the rows in the database directly by creating views
where the security is applied, so the user will always query these views
instead-of the tables. (for example, in SQL Server you can use the
suser_sname() function to retrieve the login name of the current user)

but I recommand to take a look at OLAP cubes.
this technology is better to manage and apply a good security.

>I am investigating whether there might be some commerical package that
> might meet this kind of requirements.
[quoted text clipped - 11 lines]
> "WHERE USERID="12324"  automatically placed on any query the user runs
> (presumably indirectly).
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.