Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 349
  • Last Modified:

SQL Server 2008 R2 - How to track down manual interactions

Hi and Thanks,

I am very new to all this...

I have been assigned to analize a purge project that is working and recreate it in another Database.

I am to basically copy from one database were it is working into another database.

There are Stored Procedures, Views, Tables.

I go into a Stored Procedure and can see all the parameters that are coming into the SP.

But I do not know were they are coming from or how to track them down.

I have tried a Query SQL:
SELECT *
FROM sys.procedures
WHERE OBJECT_DEFINITION(OBJECT_ID) LIKE '%@FILE_ID%'
Order by name

@File_Id is one of the parameters

but as you can see this SQL only shows SP's

This is done all within SQL Server 2008 R2

I am trying to find were it would be that the user enters in all the necessary parameters???

Please Help...
0
Amour22015
Asked:
Amour22015
  • 5
1 Solution
 
Koen Van WielinkIT ConsultantCommented:
This might be a very basic question, but how is the purge activated? Is it a user doing it? If so, how? Through another software? Or is it perhaps a scheduled job which executes periodically?
0
 
Amour22015Author Commented:
the fact that a co-worker that has some history of the project says it runs manually tells me that it has to have a user doing it.

looks like the co-worker does not want to give me all the details about this purge project.

When I first received this task, the co-worker apparently lead me on a wild goose chase involving SSIS packages.  Because when I mentioned SSIS packages being involved with my supervisor, the supervisor's response was "as far as I know SSIS is not involved with this project".

I am just wondering if there is a way to find out were the project starts???  maybe some way of back tracking from the SP's???

thanks
0
 
Amour22015Author Commented:
Ok,

When I do this SQL Query:
SELECT *
FROM [PROCLAIM].sys.objects
WHERE OBJECT_DEFINITION(OBJECT_ID) LIKE '%@FILE_ID%'
Order by name

I get this:
DF_INFLIGHT_CED_TERM_INSRT_TS      1396200024      NULL      1      1380199967      D       DEFAULT_CONSTRAINT
INFLIGHT_CED_TERM      1380199967      NULL      1      0      U       USER_TABLE
PK_CLAIM_KEY      1378103950      NULL      1      1362103893      PK      PRIMARY_KEY_CONSTRAINT
usp_JOBSTREAM_INFORMATION_I      1412200081      NULL      1      0      P       SQL_STORED_PROCEDURE

@FILE_ID = One of the parm within a SP

Thanks
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Amour22015Author Commented:
This is a better copy of the out come of the Query:
Name                                                             Type
DF_INFLIGHT_CED_TERM_INSRT_TS      DEFAULT_CONSTRAINT
INFLIGHT_CED_TERM                       USER_TABLE
PK_CLAIM_KEY                                         PRIMARY_KEY_CONSTRAINT
usp_JOBSTREAM_INFORMATION_I      SQL_STORED_PROCEDURE

thanks
0
 
Amour22015Author Commented:
I just took the bold approach and asked the co-worker:

This might be a very basic question, but how is the purge activated? Is it a user doing it? If so, how? Through another software? Or is it perhaps a scheduled job which executes periodically?

I did not think I would get an answer and would be left hanging..


But it turns out the co-worker

did not know
said that it did not matter
cause it is all going to change.

It would have been nice if they mentioned that before at the start when I was assigned...

I want to think you for your help....
0
 
Amour22015Author Commented:
Thanks
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now