April 23, 2015 at 8:12 am
Hi
I am moving all of my data from an old SQL 2000 Enterprise to SQL 2012 Enterprise. What I need is to map all of the views and tables that are used and where, and if possible, cross database.
With this info, I can then prioritise the data to be moved to the new server and which views to re-write or kill.
Any code that can do this? I already have the list of all of the SP,Views and Tables, just need to join them together now.
thanks
April 23, 2015 at 11:31 am
Disclaimer: I do NOT work for Redgate
Your easiest bet might be to invest in SQL dependency checker (yes - it's from RedGate, the parent company for this very site). It's a much cleaner interface to get to what dependencies (i.e. who's calling who) on a cross-database setting. Using the data in SQL's internal dependency checking was not as reliable; even when the dta is accurate, it doesn't give you the nice visualization tool to see and track down the links you need to adjust.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply