One way would be to craete a new user in NT and restrict login to the time window, and then only grant insert permissions on the table to this user.
better, though, would be to achieve this at DB level. Is this possible?Why would you ever need to do this at the DB level?
You might be able to set up a trigger to remove the inserted row after it is added if the time is in a range.
Better would be to have your application logic restrict access to the insert statement between certain times.
We are incorporating some OLAP cubes into our secure website and what to restrict the cubes information base on the person or client logged in. We are using Dundas OLAP as the front end for displaying the cubes. The Roles approach is not a viable solution since it is impossible for us to gather and keep track of our client’s windows usernames.
Is there a way to somehow pass a value through the control or the connection string and later use this value to filter dimension members?
> Is there a way to somehow pass a value through the control or the connection string and later use this value to filter dimension members?
Yes, there is a connection string property called "Roles", where you can specify which Roles should be used.
|||I did a little bit of digging on connection string properties and came across this in one of your blogs.
There is a new MDX function for SSAS 2005 called “CustomData”.
http://sqljunkies.com/WebLog/mosha/archive/2005/10/11/mdx_functions_as2005.aspx
I am using the “Roles” and “CustomData” properties of the connection string to achieve my purpose.
Thanks Mosha
