customer wants to remove power user (was "Need some advise")

Hi everyone,

I have a customer that wants to remove a power user
from her company.

She has given him the SA password (against my advise)
and he has his own user account setup in the database.

I am not sure if he has created any backdoor(s) into the
SQL box or not - I left him kinda on his own and didn't
pay too much attention to him.

I assume people have faced this problem before,
and i am looking for a best practices or "here is what we did"
post mortem of how they handled the issue.

thanks
tonyChange the sa password (you have no apps accessing via sa right)?

Check all the high permissions roles (sysadmins, securityadmins etc) and account for all the logins associated with them. Be very suspicious of any that are not domain accounts.

That would do for starters.

Future ref - always give permissions like that to domain accounts not SQL ones.|||The Flump speaks wisdom.

Also check for any new SQL Agent jobs.|||Thanks for the info -

Agent jobs was checked and double checked.

Also did a grep on the stored procs for any create users references

I am going to make a backup of the database and restore it
into a virtual machine, change the SA and the users password
without deleting the user.

I will leave the server running for a day or so looking for issues before the production server is touched.

Thanks again for ALL the hep!

take care
tony|||The Flump speaks wisdom.
Shouldn't this already be in his sig by now? :p

Custom data processing logic

We are developing a web application that has to do a significant amount of
data processing before a report can be run. Please would someone advise me as
to the best place to put this custom data processing logic. Should I do it in
my app beforehand or is there an appropriate hook in the report processing
lifecycle?
Further info:
- The processing involves copying data to snapshot tables and then
enriching this data: the processing is complex and varies depending on the
user.
- We will use security extensions for Forms authentication and custom
authorization.
- We would like the user to be able to use the drill-down feature so would
want to use the web-based Report Viewer.
Any help would be greatly appreciated.
StuHello Stu,
Based on my experience, I suggest you to process your data first when your
user login or just after the login process.
After that, you could show the report.
My suggestion of the report view control is that you use the local report
in your application so that the report will use your custom authentication
and you do not need to customize the authentication in the report server.
All this is to avoid the slow performance of the report to the user.
Please let me know if you have any question.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Since it is a complex processing and moreover you have developed a web
application, do it in your application and get the final results to be
displayed, that will be faster, so RS will be used for reporting the end
results. Why the processing in your custom applications is that you get very
good flexibility like massaging the data, and filtering as per the user
etc... Finally the reporting part with layout, format, drilldown etc..can be
done using RS.
Amarnath, MCTS.
"Stu" wrote:
> We are developing a web application that has to do a significant amount of
> data processing before a report can be run. Please would someone advise me as
> to the best place to put this custom data processing logic. Should I do it in
> my app beforehand or is there an appropriate hook in the report processing
> lifecycle?
> Further info:
> - The processing involves copying data to snapshot tables and then
> enriching this data: the processing is complex and varies depending on the
> user.
> - We will use security extensions for Forms authentication and custom
> authorization.
> - We would like the user to be able to use the drill-down feature so would
> want to use the web-based Report Viewer.
> Any help would be greatly appreciated.
> Stu|||Thanks. I will look into using the report viewer control.
"Wei Lu [MSFT]" wrote:
> Hello Stu,
> Based on my experience, I suggest you to process your data first when your
> user login or just after the login process.
> After that, you could show the report.
> My suggestion of the report view control is that you use the local report
> in your application so that the report will use your custom authentication
> and you do not need to customize the authentication in the report server.
> All this is to avoid the slow performance of the report to the user.
> Please let me know if you have any question.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Stu,
Thanks for the update. If you have any question , please feel free to let
me know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.