|
Home > Archive > MS SQL Server > April 2006 > Profiler Question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| I have a database that's being restored on a monthly basis, but I think this process is overkill.
The users are using a few tables or whatever to run reports using Crystal Reports, and accessing tables via MS Access.
What do I profile for to 'see' everything that is being used in this database so that I can restore only these objects as opposed to the entire db?
I have only used profiler to do some query statement troubleshooting, 'Stored Procedure Compelted', but other than that am not proficient with profiler.
All suggestions are greatly appreciated!!!!
| |
| Kevin3NF 2006-03-31, 1:23 pm |
| You don't mention where teh db is being restored and why, or really what the
ultimate goal is. Backup and restore is probably the easiest way to refresh
a Dev environment. Replication or Log shipping might be best for a reporting
server.
Your question: To see everything accessed, at a minimum get these:
Stored procedures: RPC:Completed
T-SQL: SQL:Batch Completed
Basically, the default trace with Security Audit and Sessions removed
Assumes you only care about sp calls and table access. However, if a sp
references a dozen tables, you will not see that in the trace.
"Jude" wrote:
> I have a database that's being restored on a monthly basis, but I think this process is overkill.
>
> The users are using a few tables or whatever to run reports using Crystal Reports, and accessing tables via MS Access.
>
> What do I profile for to 'see' everything that is being used in this database so that I can restore only these objects as opposed to the entire db?
>
> I have only used profiler to do some query statement troubleshooting, 'Stored Procedure Compelted', but other than that am not proficient with profiler.
>
> All suggestions are greatly appreciated!!!!
| |
| John Bell 2006-04-02, 7:23 am |
| Hi
If you have the code in stored procedures then why not trawl through those
to see what they call, sp_depends may give you some idea but not necessarily
everything.
If you have a naming convention and the stored procedure code in version
control then you can easily do text searches. Even if you do isolate the
tables used, it will be a more complicated restoration process.
John
"Jude" wrote:
> I have a database that's being restored on a monthly basis, but I think this process is overkill.
>
> The users are using a few tables or whatever to run reports using Crystal Reports, and accessing tables via MS Access.
>
> What do I profile for to 'see' everything that is being used in this database so that I can restore only these objects as opposed to the entire db?
>
> I have only used profiler to do some query statement troubleshooting, 'Stored Procedure Compelted', but other than that am not proficient with profiler.
>
> All suggestions are greatly appreciated!!!!
|
|
|
|
|