Obscuring T-SQL code from RDL File and SQL Server

I would like to write some reports that will query T-SQL for information, but
I don't what anyone to be able to see the T-SQL code. So I can not store the
T-SQLin the RDL file, or put it in a SP. Also can't even use and encrypted
SP because someone would have to have the source code to create the T-SQL.
So what options are available to hide the T-SQL code, but not allow anyone to
see it, or change it?On Apr 17, 7:50 pm, Greg Larsen <gregalar...@.removeit.msn.com> wrote:
> I would like to write some reports that will query T-SQL for information, but
> I don't what anyone to be able to see the T-SQL code. So I can not store the
> T-SQLin the RDL file, or put it in a SP. Also can't even use and encrypted
> SP because someone would have to have the source code to create the T-SQL.
> So what options are available to hide the T-SQL code, but not allow anyone to
> see it, or change it?
As far as I know, there is not really much else that can be done to
restrict access to the T-SQL or stored procedure(s). Sorry that I
could not be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||I would guess if a compiled piece of code could be used as a datasource then
potentially this might work. Don't suppose you know how to create a piece of
compiled code that can be used as a data source to a reporting services
report.
"EMartinez" wrote:
> On Apr 17, 7:50 pm, Greg Larsen <gregalar...@.removeit.msn.com> wrote:
> > I would like to write some reports that will query T-SQL for information, but
> > I don't what anyone to be able to see the T-SQL code. So I can not store the
> > T-SQLin the RDL file, or put it in a SP. Also can't even use and encrypted
> > SP because someone would have to have the source code to create the T-SQL.
> > So what options are available to hide the T-SQL code, but not allow anyone to
> > see it, or change it?
> As far as I know, there is not really much else that can be done to
> restrict access to the T-SQL or stored procedure(s). Sorry that I
> could not be of further assistance.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>