Menu
▾
▴
#19 Cross-platform global settings
In the developing phase of the HIPAA project, Neil
stated at least three times that global settings will
continue to be a problem for all future solutions; and,
we should standardize them. Fixing that problem was
not in the scope of the project.
To summarize Neil's vision, there must be a way:
1. To document locally-specified settings like the
localsettings.asp.
2. It must be accessible across multlple platforms and
solutions (.VBS, .BAS, .DTS, .ASP, and .ASPX).
3. It must be "discoverable" by each of these platforms
to reduce the administrative overhead of maintaining
disparate configurations.
In philosophy. this problem is described as the "First
Cause" -- philosophers have not been able to solve it
yet. I'll be interested in seeing how developers and
administrators do it.
Logged In: YES
user_id=97668
(On Vamsi's behalf)
I think I have a working prototype to deploy DTS packages
with out the use of ini files.
This is my vision of how this works:
We use a global variable in every DTS package to hold the
SQL server name.
All other variables will be stored in a table, and use the Query
to get the value ( These variables are not saved in the
localsettings.asp so we cannot use that; example : location
where the .dat files are stored)
I have a prototype application that will help to deploy and
save the DTS from source server to destination server,
instead of manually saving the DTS from .dts file.
A web page or a windows application will list all the DTS
packages from a table in the database whose global variable
needs to be changed, by checking the check boxes and
clicking save changes the sql server global variable.
By doing this way we are not using any .ini files and no need
to open the DTS package to make any changes.
Logged In: YES
user_id=97668
Formal requirements will be defined; this project will be
developed by the developers in the San Antonio office; and,
this project will be contributed to the Sourceforge library.