Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
clarkbaker1964
Constraint Violating Yak Guru
428 Posts |
 Posted - 2005-01-05 : 15:37:20
|
I have been monitoring my server processing by recording the programs that are accessing the box how can I take this information and query for the originating DTS package description.SQLAgent - TSQL JobStep (Job 0xF6B4FB62EB9DAE46A88DE7975311BA1E : Step 1)Also a few weeks ago someone had a suggestion for killing any connections that did not come from "Known programs" I would like to control my access points does anyone have this link I could'nt find it with the search features. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-01-05 : 15:40:24
|
| Someone scheduled the package via the wizard so that's why you see that GUID. You can find the DTS package's name via msdb.dbo.sysdtspackages.I wouldn't recommend killing connections from unknown programs. What I would recommend is finding out why those programs are connecting and why the DBA doesn't know about them. You can kill connections via KILL <spidNo>. You can find out information about the connections via master.dbo.sysprocesses.Tara |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-01-06 : 00:30:25
|
| we're currently using a tracking table for user/roles - applications,processes with applications not in the list and not within the specified subnet or domain will be "killed",but the best way is to restrict the users, or secure the ini files--------------------keeping it simple... |
|
|
|
|
|
|
Audit DTS Packages