March 19, 2012 at 8:56 pm
Thanks very much everyone for taking the time to give me advice.
Data services, project managment and development met today and made a two step deal; we are going to move the essential by one of either a fast track method or the trail of tears method.
1) Fast track means new work produced according to our processes (have headers, were peer reviewed & docd move immediately
2) Trail of tears means legacy work produced without portfolio must go through profiler or odbc log with a developer, pm and a data services resource (jr dba or etl engineer) to shake down the unknown collaboratively, so no one gets stuck owning the orphan just because they touched it. if the unknown cannot be satisfactorily documented because of missing source or undecompilable or other impasse, it will be allowed to run out its life as it is, where it is, but will not be migrated.
We believe most access we know about is via stored procedures, and that most ssis jobs have configuration files pointing to server names, and that we discourage local SQL in SSRS, so we decided to keep two instances alive so we can weed out what we dont want. We have another critical business system running on a windows 2000 server with SQL Server 2000...its the only application on it, but its also the only way it will run, so the notion of triage til it dies is not unknown.
The best outcome was the collaboration agreement between the project managers, developers and data services to dedicate resources to figure out the unknown together...a luxury i which i luxuriate <g>
thank you again for your collective wisdom...this is an enormous resource if only you just ask the right question.
drew
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply