• procs and views referencing your tables are only part of the puzzle;

    applications can have dependencies on those tables, and applications can reference tables that are never used.

    there's a handy chartabout how 45% of application improvements get added but are never used, and those improvements most likely reference objects int ehd atabase which need to exist, but are never used as well.

    you'll need to search applcation code in addition to the database.

    here's a handy script for you for the SQL side:

    SELECT

    depz.referenced_schema_name,

    depz.referenced_entity_name,

    objz.type_desc,

    object_schema_name(depz.referencing_id) As ReferencingSchema,

    object_name(depz.referencing_id) AS ReferencingObject,

    colz.name AS ColumnName

    FROM sys.sql_expression_dependencies depz

    INNER JOIN sys.objects objz ON depz.referenced_id=objz.object_id

    LEFT OUTER JOIN sys.columns colz ON objz.object_id = colz.object_id

    AND colz.column_id = referencing_minor_id

    --WHERE referencing_id = OBJECT_ID(N'MyTable');

    WHERE referenced_id = OBJECT_ID(N'EDLogDetail');

    --AND colz.name = 'EmployeeNumber'

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!