Utilizing SQL with WindMilMap

Transcription

1 Utilizing SQL with WindMilMap Presented by Eric Kirkes, GIS Support Specialist

2 This presentation will provide basic information on how to manage a SQL database tied to your Milsoft model. Schema and structure of tables and database Import data External table manager set up Common issues 2

3 Why is this knowledge useful to Milsoft customers? Analyze, edit and view SQL data across core E&O platforms Export data to separate platforms 3

4 SQL Server Management Studio SQL Server Management Studio (SSMS) is used to configure, manage, and administer components with SQL Server. Use SQL Server to store Milsoft external tables Installed on your SQL or GIS server by default Credential based security and log in 4

5 Schema and Structure Object Explorer Can create new items Database Ø Tables Ø Fields Ø Name(datatype), allow nulls 5

6 Object Explorer Database Design Window Comes up when Name(datatype), allow nulls creating new table or adding field Assign Column Name, Data Type, Allow Nulls Set Primary Key 6

7 7 Add column Right click columns folder New column Use Design view Delete column Right click column name Delete Can also delete in design

8 Importing Data Import and Export Wizard 8

9 9 Example import Import Pole_Inspection_2018.xls Choose data source Choose destination database

10 10 Specify Table Copy or Query Select tables to import Edit mappings of imported fields Preview Useful to see how the the table will look

11 11 Finish to perform following actions New table is created Append to existing

12 12 Result: New table created with imported pole inspection data Can rename the table and columns

13 Query to see all imported data from new table select * from pole_inspection_

14 14 Append import to existing table Add new fields to table before import if necessary Map destination table in import wizard

15 Edit Mappings if field names are different Preview 15

16 New rows will be appended to the existing table 16

17 Setting Up the External Table Manager Links SQL database with Milsoft model Where is it? Windmil: Preferences -> External Table Manager WindMilMap: WindMilMap -> External Table Manager WindMil WindMilMap 17

18 18 Step 1: Create database connection Use Microsoft OLE DB Provider for SQL Server

19 19 Link to SQL Server 1) Server name or IP 2) SQL log in credentials 3) Select database 4) Test connection

20 Test connection results Successful connection Invalid user name or password 20 Invalid server name or IP

21 21 Database connection string Shows server name and log in credentials Important options Enabled Read-Only Create Row With Feature Delete Row With Feature

22 Step 2: Create link to imported table 1) Choose database connection 2) Choose external table 3) Move fields to Used Fields 4) Primary Key 5) Element Key Link between table and the model.. Element name or Element GUID My PoleNo field is the Element Name 22

23 23 Step 3: Field Mappings Choose editable fields Map WindMil fields to SQL fields Alias

24 24 Step 4: Table Uses Map table links to WindMil type

25 Result: View linked SQL data across Core E&O platform Query, edit, export, and analyze inside of WindMil and WindMilMap External tab in the Map Point Editor 25

26 26 Attribute table and window in WindMilMap

27 27 External table viewer

28 28 Add new field 1) Add new field in Design view in SSMS 2) Find new field under Available Fields 3) Move to Used Fields 4) Make editable in Field Mappings

29 Delete field 1) Delete field from table in SSMS 2) Move to Available Fields Step 1 Step 2 Result 29

30 Setting Up Multi-Relational Tables Multiple records per table 30

31 31 WMREC_ID as Primary Key CMID as Element Key Uniqueidentifier datatype

32 32 WMREC_ID and CMID populated automatically CMID is the same for all associated records

33 33 Multiple tables per element type

34 34 Multiple tables per type in Table Uses

35 Common Issues SQL truncation error when posting a project Input is too long for designated SQL datatype Example: Enter a Pole_No that is 7 digits but the datatype is set to nvarchar(5) 35

36 1)Check error browser Windmil WindMilMap Find element name 36

37 37 Fb 2)Find fields edited in project properties

38 3)Use SSMS to check field datatypes Change datatype to appropriate length Before After 38

39 Importing duplicate values into a Primary Key field Common if you don t have Primary Key actually set Example: Try to set CMID as Primary Key in Pole table Past import had duplicate CMID 39

40 1)Find duplicate values Select CMID from Pole Group by CMID having Count(*)>1 40

41 2)Select duplicate records SELECT * FROM Pole WHERE CMID = '3C06BF0E-94DA-11E7-A E0F27E' 41

42 3)Delete unwanted duplicates Delete from Pole where Pole_No = '

43 43 Result: Set Primary Key for Pole table to CMID

44 44 Domain values Automatically domains unique values Add a domain value Post project with new value Delete a domain value Query and replace the value in SSMS, Select by Attributes, or the Selected Elements Window

45 45 Symbolize using external fields in WMM

46 Update fields from different data source 1) Import dataset as new table 2) Perform an Update/Join query Example: Adding pole inspection data to main Pole table update table1 set table1.field=table2.field from table1 inner join table2 on table1.field=table2.field 46

47 update Pole set Pole.Height=Pole_Inspection_2018.Height from Pole inner join Pole_Inspection_2018 on Pole.pole_no=Pole_Inspection_2018.PoleNo Repeat for necessary fields 47

48 Making A Back Up.bak file extension Tasks -> Back Up \Program Files\Microsoft SQL Server\ MSSQL11.MSSQLSERVER\MSSQL\Backup\ Automate by creating a job in SQL Server Agent 48

49 Restoring A Back Up Tasks -> Restore -> Database Restore Device (.bak) Multiple kinds of backups 49

50 Contact Information Eric Kirkes

51 51

52 52