×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I had a question today about what the best approach was for designing and
building stored procedures in different scenarios. For example, in a Test
and Dev environment (multiple different versions), or a production
environment that uses different data libraries for company or division data
but a common code base (one version, different data libraries.
Would it be better to create a Stored procedure for each environment ?
Should/can the Stored procedure be designed so it resolves the library based
library list ?
Should the library be passed in as a parameter ?
Should I even use a stored procedure in this scenario ?
What kind of versioning strategy if any could I used with stored procedures
?
This is a somewhat hypothetical question for me but I'm interested in any
and all viewpoints about how best to manage stored procedures so any
feedback is welcome.
If you want me to phrase my question better or elaborate on something go
right ahead and ask,
Regards
Evan Harris
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
