Laserfiche WebLink
<br />South ptatte Water Rights Management System <br /> <br />,0.1 4',' ll~ <br /> <br />~-- <br />Dbc...sc. Cp""...., At-lb$ : <br /> <br />US~ <br /> <br />J;,".~< 1. <br />+0 ~__,__, scl\ <br /> <br />corY <br /> <br />Il-I\$ 15N'''T* 3. <br />'NEEbEl:> <br /> <br />IRs, U~I.J)",,,() 'REc.oil.l:>S To "BAC."l.tr:- S. <br />:'lkE.. <br />(L) Ul>Jl...OAl) 'To. <br />':::EL.tC::T .. FRoM ~~s-. ...i'3\"~S <br /> <br />Table Source <br />use_codes Generated at CADSWES <br />wis_comments Input by user <br />wis_data Input by user <br /> <br />Table 2: Data Sources <br /> <br />1,3 Relational Database Maintenance <br /> <br />In some cases, it may be necessary to update the data in the set of static tables, such as <br />when the SEO creates a new version of the water rights tabulation as the result of Water <br />Court decrees. Only the data contained in the static tables should be changed--<:olumn <br />structure must not be altered. In almost all cases, changes to table columns require corre- <br />sponding changes to the SPWRMS application software and should be done in close <br />consultation with programming maintenance personnel. Data in the dynamic tables are <br />maintained by the application itself and should not be modified outside of the application. <br /> <br />Water Rights Tabulation <br /> <br />A yearly migration of the SEO water rights tabulation from DBase to the SPWRMS data- <br />base is expected. This procedure is straightforward as long as the source DBase files are <br />not corrupt. In the past, however, odd characters in the files have made conversion of the <br />data very difficult. In addition, there are non-unique rows in some DBase files which <br />violate constraints in place on the SPWRMS database tables. These constraints prevent <br />duplicate rows in the water rights table. These obstacles must be handled on a <br />case-by-case basis. <br /> <br />In order to perform the migration of the water rights tabulation from DBase to Informix. <br />the following steps must be performed: <br /> <br />2. <br /> <br />Export the data for each district to a text file. Using DBase. export the data for <br />each table to a text file using FIXED-WIDTH FIELD output type. This is an option <br />available through the DBase menu system. """.t{~ <br /> <br />Transfer the text files to the UNIX database server. Use a file transfer utility such <br />as ftp to move the files to the host machine of the SPWRMS database (currently <br />DbServerat SEO). IfrE ASCJI Tro "'.rE ftt. <br /> <br />Convert the text files to UNIX file format. Use the utility dos2unix to perform this <br />conversion. <br />EXAMPLE: dos2unix rights23.txt > rights23.unix <br /> <br />Rnn the UNIX script cutt. rights to prepare file for input. This script, written <br />by CADSWES, adds pipe deli miters to the file, which enables SPWRMS database to <br />use the file as input. /"', J,"J> I, I JO"5' /-/v.!, <br />EXAMPLE: cutt.rights rights23.unix > rights23.input <br /> <br />Delete the current water rights table from SPWRMS database. <br />EXAMPLE: DELETE FROM phS_rights W\.\ERE wt> ~ ~ <br /> <br />Use Informix utilities to load the file. Simple SQL statements will load a text file of <br />this format into the database. <br /> <br />4. <br /> <br />6. <br /> <br />12 <br /> <br />Database Manual <br /> <br />~ 1+ c("t>Ol" oCCU"'-$ w~',\,- \o....J.'.....5 d.,.;.....,<....~ <br />DELETE FRtl""" ~\iS _ A.\(,tH.,. t <br />WHE fl.€: IN t> ~ '---' <br />