Changes

Jump to: navigation, search

Post Processing SQL Scripts

895 bytes added, 12:40, 14 November 2017
no edit summary
'' Example of retrieving information from a linked table''
</div>
{{Note | It is only the Country Structure of Locations that is flattened, other Country structure references (both system and CDFs) have to be retrieved by SQL views.}}
[[Image:SAG CS flattening1.png|300px|center]]
<div align="center">
<li> Your script will automatically be applied in the end of the database generation.
</ol>
 
{{Note| The Post Processing SQL scripts including SQL views needs to be re-applied '''every''' time a staging area database is updated i.e. re-created. <br/>
I you would like to test a SQL script without running the Staging Area Generator (of course only works if there is an '''existing''' staging database):
# Open a command window
# Go to ''C:/IMSMAETLTool''
# Run the following in the command window: pgsql\bin\psql -U imsma -d staging -h localhost -L sql.log -f sqlscripts\filename.sql }}
 
[[Image:PostProc SAG error.png|600px|center]]
<div align="center">
'' SAG cannot find the script file ''
</div>
# The post processing SQL file must be stored in C:\IMSMAETLTool\sqlscripts
# The full name of the file must be specified e.g. Albania_stat.sql
# The SAG must be started via a shortcut. You find which values to use for the shortcut '''[[Windows 8 and Windows 10#Shortcuts |here]]'''.
Contact your [[Information Management Team | GICHD IM advisor]] for help in developing SQL statements according to specific requirements.
{{NavBox Business Intelligence}}
[[Category:VIE]]
6,632
edits

Navigation menu