Our developers love to create lots of different stored procedures/views, which extracts data from lots of different databases on different servers.
Every time we migrate to a new database server, something breaks because some obscure procedure or view didn't get fixed at the same time. Documenting them all is already underway.. I still have to ask - isn't there a simpler way of doing this?
Would it be possible for a stored procedure to extract the connection string from a table - let's say "dbo.linked-databases", and have a unique row per database being references, where one of the columns specify the connecting string? Can stored procedures then SELECT this, and expand it as a variable?
Sorry if the question doesn't make any sense, as I'm quite new with SQL.