Database Updates---------------------------------------------------------------------------------------------WARNING! In general, script modifications should not be made at the time-series hostapplication level (e.g., SIEGate or openPDC) - these scripts will be overwritten duringthe automated Grid Solutions Framework dependency roll-down process. It is expected thatchanges to the primary schema will be made in GSF then rolled-down to all time-seriesimplementations. Custom script modifications should go in an independent local scriptto be run after the initial schema setup.---------------------------------------------------------------------------------------------Updating the Grid Solutions Framework databases requires a number of steps, enumerated below.There are five database types supported: MySQL, Oracle, SQL Server, PostgreSQL and SQLite. 1) Open GridSolutionsFramework.sln 2) In the 'Data' folder in the GSF.TimeSeries project and select the sub-folder for the database type you wish to edit - GSFSchema.sql contains the primary schema 3) Edit the schema as needed - repeat for other databasesTo initialize the SQLite databases: 4) Close the solution to avoid any conflicts 5) Open the command prompt and navigate to the ...\Data\SQLite folder 6) Run "db-update force"To update the SerializedSchema.bin used by the Data Migration Utility: 7) Load a new blank schema (i.e., GSFSchema.sql) into SQL Server 8) Run the Data Migration Utility 9) Select SQLServer from the Data Type list for the "From Connect String"10) Answer "Yes" to verify connection string replacement question11) Answer "No" to verify connection string type question for OLE DB12) Update the from connection string to connect to your new GSF Schema, for example: Provider=SQLOLEDB; Data Source=localhost\SQLEXPRESS; Initial Catalog=GSFSchema; Integrated Security=SSPI13) Click the from connection string "Test" link, if this succeeds a "Serialize" button will be visible on the application14) Click the "Serialize" button to create a new "SerializedSchema.bin", the updated file will be located in the DataMigrationUtility.exe path15) Check out and replace the "...\GSF.TimeSeries\Data\SerializedSchema.bin" file with the new updated file16) Check in the replaced "...\GSF.TimeSeries\Data\SerializedSchema.bin" fileYour database changes are now complete!You will need to run roll-down scripts for specific projects to make sure schema changesare applied to specific time-series implementations.
Database Updates
---------------------------------------------------------------------------------------------
WARNING! In general, script modifications should not be made at the time-series host
application level (e.g., SIEGate or openPDC) - these scripts will be overwritten during
the automated Grid Solutions Framework dependency roll-down process. It is expected that
changes to the primary schema will be made in GSF then rolled-down to all time-series
implementations. Custom script modifications should go in an independent local script
to be run after the initial schema setup.
---------------------------------------------------------------------------------------------
Updating the Grid Solutions Framework databases requires a number of steps, enumerated below.
There are five database types supported: MySQL, Oracle, SQL Server, PostgreSQL and SQLite.
1) Open GridSolutionsFramework.sln
2) In the 'Data' folder in the GSF.TimeSeries project and select the sub-folder for the
database type you wish to edit - GSFSchema.sql contains the primary schema
3) Edit the schema as needed - repeat for other databases
To initialize the SQLite databases:
4) Close the solution to avoid any conflicts
5) Open the command prompt and navigate to the ...\Data\SQLite folder
6) Run "db-update force"
To update the SerializedSchema.bin used by the Data Migration Utility:
7) Load a new blank schema (i.e., GSFSchema.sql) into SQL Server
8) Run the Data Migration Utility
9) Select SQLServer from the Data Type list for the "From Connect String"
10) Answer "Yes" to verify connection string replacement question
11) Answer "No" to verify connection string type question for OLE DB
12) Update the from connection string to connect to your new GSF Schema, for example:
Provider=SQLOLEDB; Data Source=localhost\SQLEXPRESS; Initial Catalog=GSFSchema;
Integrated Security=SSPI
13) Click the from connection string "Test" link, if this succeeds a "Serialize"
button will be visible on the application
14) Click the "Serialize" button to create a new "SerializedSchema.bin", the updated
file will be located in the DataMigrationUtility.exe path
15) Check out and replace the "...\GSF.TimeSeries\Data\SerializedSchema.bin" file
with the new updated file
16) Check in the replaced "...\GSF.TimeSeries\Data\SerializedSchema.bin" file
Your database changes are now complete!
You will need to run roll-down scripts for specific projects to make sure schema changes
are applied to specific time-series implementations.