SqlChangeAutomation.dll-Help.xml

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
<?xml version="1.0" encoding="utf-8"?>
<helpItems schema="maml" xmlns="http://msh">
  <!-- Cmdlet: Invoke-DatabaseBuild -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Invoke-DatabaseBuild</command:name>
      <command:verb>Invoke</command:verb>
      <command:noun>DatabaseBuild</command:noun>
      <maml:description>
        <maml:para>Builds a database project.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Invoke-DatabaseBuild cmdlet builds a database project by checking the database definition can be deployed to an empty database. It the build is successful, the cmdlet creates an IProject object that represents the built project.</maml:para>
      <maml:para>The cmdlet will throw an exception if the project cannot be deployed to an empty database.</maml:para>
      <maml:para>By default, the cmdlet creates a temporary copy of the database on LocalDB. Alternatively, you can use the TemporaryDatabaseServer parameter to specify a SQL Server instance for the temporary database. This is useful if your database uses features that aren't supported by LocalDB, such as Full-Text Search.</maml:para>
      <maml:para>If you don't want to use LocalDB and don't have permission to create a database on the SQL Server instance, you can use the TemporaryDatabase parameter to specify an existing database.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: TemporaryDatabaseServer -->
      <command:syntaxItem>
        <maml:name>Invoke-DatabaseBuild</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The path to the database project to validate.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when validating the schema.</maml:para>
            <maml:para>This parameter will be ignored if the value specified is either $null or empty.</maml:para>
            <maml:para>For more information about filtering see https://www.red-gate.com/sca/ps/help/filters.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>Tells the SQL Compare engine to ignore parser errors.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: QueryBatchTimeout -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>QueryBatchTimeout</maml:name>
          <maml:description>
            <maml:para>The execution timeout, in seconds, for each batch of queries in the script for validation. The default value is 30 seconds. A value of zero indicates that no execution timeout will be enforced.</maml:para>
          </maml:description>
          <command:parameterValue required="true">int</command:parameterValue>
          <dev:type>
            <maml:name>System.Int32</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>30</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when creating the script for validation. The default set of options are listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TemporaryDatabaseServer -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TemporaryDatabaseServer</maml:name>
          <maml:description>
            <maml:para>The connection string for the temporary database server used for validation. For example, 'Data Source=TempServer01'.</maml:para>
            <maml:para>By default, LocalDB is used for the temporary database. However there may be some features in your database that aren't supported by LocalDB (for example, Full-Text Search). In this case, or if LocalDB isn't present, use this parameter to specify an alternative SQL Server instance for the temporary database.</maml:para>
            <maml:para>LocalDB is not supported when using a SQL Clone image as a baseline. Therefore, you must specify a temporary database server (or a temporary database). For more information, see http://www.red-gate.com/sca/ps/help/clonebaseline.</maml:para>
            <maml:para>Using this option, SQL Change Automation will create a temporary database on the specified SQL Server instance.</maml:para>
            <maml:para>You can't use this parameter in addition to the TemporaryDatabase parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseServerConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseServerConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TransactionIsolationLevel -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TransactionIsolationLevel</maml:name>
          <maml:description>
            <maml:para>Use this parameter to specify the isolation level for the transactions during the temporary deployment for validation. Permitted values are: Serializable, Snapshot, RepeatableRead, ReadCommitted and ReadUncommitted. The default level is Serializable.</maml:para>
            <maml:para>See https://docs.microsoft.com/sql/t-sql/statements/set-transaction-isolation-level-transact-sql for more details on transaction isolation levels.</maml:para>
            <maml:para>Possible values: Serializable, Snapshot, RepeatableRead, ReadCommitted, ReadUncommitted</maml:para>
          </maml:description>
          <command:parameterValue required="true">TransactionIsolationLevel</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Shared.Domain.TransactionIsolationLevel</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>Serializable</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Serializable</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Snapshot</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">RepeatableRead</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadCommitted</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadUncommitted</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
      </command:syntaxItem>
      <!-- Parameter set: TemporaryDatabase -->
      <command:syntaxItem>
        <maml:name>Invoke-DatabaseBuild</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The path to the database project to validate.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when validating the schema.</maml:para>
            <maml:para>This parameter will be ignored if the value specified is either $null or empty.</maml:para>
            <maml:para>For more information about filtering see https://www.red-gate.com/sca/ps/help/filters.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>Tells the SQL Compare engine to ignore parser errors.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: QueryBatchTimeout -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>QueryBatchTimeout</maml:name>
          <maml:description>
            <maml:para>The execution timeout, in seconds, for each batch of queries in the script for validation. The default value is 30 seconds. A value of zero indicates that no execution timeout will be enforced.</maml:para>
          </maml:description>
          <command:parameterValue required="true">int</command:parameterValue>
          <dev:type>
            <maml:name>System.Int32</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>30</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when creating the script for validation. The default set of options are listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TemporaryDatabase -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TemporaryDatabase</maml:name>
          <maml:description>
            <maml:para>The details of the temporary database used for validation. This can be:</maml:para>
            <maml:para>- an instance of a Database Connection object produced by the New-DatabaseConnection cmdlet.</maml:para>
            <maml:para>- a database connection string. For example, 'Data Source=TempServer01;Initial Catalog=TempDatabase01'.</maml:para>
            <maml:para>By default, LocalDB is used for the temporary database. If you don't want to use LocalDB and don't have permission to create a database on the SQL Server instance, use this option to specify an existing database to use for the temporary copy of the database.</maml:para>
            <maml:para>LocalDB is not supported when using a SQL Clone image as a baseline. Therefore, you must specify a temporary database (or a temporary database server). For more information, see http://www.red-gate.com/sca/ps/help/clonebaseline.</maml:para>
            <maml:para>If you use this parameter, all existing data on the temporary database will be lost.</maml:para>
            <maml:para>You can't use this parameter in addition to the TemporaryDatabaseServer parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TransactionIsolationLevel -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TransactionIsolationLevel</maml:name>
          <maml:description>
            <maml:para>Use this parameter to specify the isolation level for the transactions during the temporary deployment for validation. Permitted values are: Serializable, Snapshot, RepeatableRead, ReadCommitted and ReadUncommitted. The default level is Serializable.</maml:para>
            <maml:para>See https://docs.microsoft.com/sql/t-sql/statements/set-transaction-isolation-level-transact-sql for more details on transaction isolation levels.</maml:para>
            <maml:para>Possible values: Serializable, Snapshot, RepeatableRead, ReadCommitted, ReadUncommitted</maml:para>
          </maml:description>
          <command:parameterValue required="true">TransactionIsolationLevel</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Shared.Domain.TransactionIsolationLevel</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>Serializable</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Serializable</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Snapshot</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">RepeatableRead</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadCommitted</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadUncommitted</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The path to the database project to validate.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TemporaryDatabaseServer -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TemporaryDatabaseServer</maml:name>
        <maml:description>
          <maml:para>The connection string for the temporary database server used for validation. For example, 'Data Source=TempServer01'.</maml:para>
          <maml:para>By default, LocalDB is used for the temporary database. However there may be some features in your database that aren't supported by LocalDB (for example, Full-Text Search). In this case, or if LocalDB isn't present, use this parameter to specify an alternative SQL Server instance for the temporary database.</maml:para>
          <maml:para>LocalDB is not supported when using a SQL Clone image as a baseline. Therefore, you must specify a temporary database server (or a temporary database). For more information, see http://www.red-gate.com/sca/ps/help/clonebaseline.</maml:para>
          <maml:para>Using this option, SQL Change Automation will create a temporary database on the specified SQL Server instance.</maml:para>
          <maml:para>You can't use this parameter in addition to the TemporaryDatabase parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseServerConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseServerConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TemporaryDatabase -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TemporaryDatabase</maml:name>
        <maml:description>
          <maml:para>The details of the temporary database used for validation. This can be:</maml:para>
          <maml:para>- an instance of a Database Connection object produced by the New-DatabaseConnection cmdlet.</maml:para>
          <maml:para>- a database connection string. For example, 'Data Source=TempServer01;Initial Catalog=TempDatabase01'.</maml:para>
          <maml:para>By default, LocalDB is used for the temporary database. If you don't want to use LocalDB and don't have permission to create a database on the SQL Server instance, use this option to specify an existing database to use for the temporary copy of the database.</maml:para>
          <maml:para>LocalDB is not supported when using a SQL Clone image as a baseline. Therefore, you must specify a temporary database (or a temporary database server). For more information, see http://www.red-gate.com/sca/ps/help/clonebaseline.</maml:para>
          <maml:para>If you use this parameter, all existing data on the temporary database will be lost.</maml:para>
          <maml:para>You can't use this parameter in addition to the TemporaryDatabaseServer parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: SQLCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Compare options to use when creating the script for validation. The default set of options are listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
          <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
          <maml:para>By default, the following Compare options are used:</maml:para>
          <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
          <maml:para>- DecryptEncryptedObjects</maml:para>
          <maml:para>- DoNotOutputCommentHeader</maml:para>
          <maml:para>- ForceColumnOrder</maml:para>
          <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
          <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
          <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
          <maml:para>- IgnoreUserProperties</maml:para>
          <maml:para>- IgnoreWhiteSpace</maml:para>
          <maml:para>- IgnoreWithElementOrder</maml:para>
          <maml:para>- IncludeDependencies</maml:para>
          <maml:para>- ThrowOnFileParseFailed</maml:para>
          <maml:para>- UseCompatibilityLevel</maml:para>
          <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: SQLDataCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLDataCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TransactionIsolationLevel -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TransactionIsolationLevel</maml:name>
        <maml:description>
          <maml:para>Use this parameter to specify the isolation level for the transactions during the temporary deployment for validation. Permitted values are: Serializable, Snapshot, RepeatableRead, ReadCommitted and ReadUncommitted. The default level is Serializable.</maml:para>
          <maml:para>See https://docs.microsoft.com/sql/t-sql/statements/set-transaction-isolation-level-transact-sql for more details on transaction isolation levels.</maml:para>
          <maml:para>Possible values: Serializable, Snapshot, RepeatableRead, ReadCommitted, ReadUncommitted</maml:para>
        </maml:description>
        <command:parameterValue required="true">TransactionIsolationLevel</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Shared.Domain.TransactionIsolationLevel</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>Serializable</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Serializable</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Snapshot</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">RepeatableRead</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">ReadCommitted</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">ReadUncommitted</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
      <!-- Parameter: FilterPath -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>FilterPath</maml:name>
        <maml:description>
          <maml:para>The path to a .scpf filter file.</maml:para>
          <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when validating the schema.</maml:para>
          <maml:para>This parameter will be ignored if the value specified is either $null or empty.</maml:para>
          <maml:para>For more information about filtering see https://www.red-gate.com/sca/ps/help/filters.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: QueryBatchTimeout -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>QueryBatchTimeout</maml:name>
        <maml:description>
          <maml:para>The execution timeout, in seconds, for each batch of queries in the script for validation. The default value is 30 seconds. A value of zero indicates that no execution timeout will be enforced.</maml:para>
        </maml:description>
        <command:parameterValue required="true">int</command:parameterValue>
        <dev:type>
          <maml:name>System.Int32</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>30</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: IgnoreParserErrors -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreParserErrors</maml:name>
        <maml:description>
          <maml:para>Tells the SQL Compare engine to ignore parser errors.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The path to the database project to validate.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: IProject -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$project = "C:\Work\project\project.sqlproj"
$validatedProject = $project | Invoke-DatabaseBuild</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Invoke-DatabaseBuild cmdlet to build a SQL Change Automation project.</maml:para>
          <maml:para>A temporary copy of the database is created on LocalDB. If the project content is invalid, this operation will throw an exception. Otherwise, it will output an instance of an IProject object that can be used as the input for other SQL Change Automation cmdlets.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$validatedProject = $project | Invoke-DatabaseBuild</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Invoke-DatabaseBuild cmdlet to validate the schema and static data of a SQL Source Control project.</maml:para>
          <maml:para>A temporary copy of the database is created on LocalDB. If the project content is invalid, this operation will throw an exception. Otherwise, it will output an instance of an IProject object that can be used as the input for other SQL Change Automation cmdlets.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$project = "C:\Work\project\project.sqlproj"
$validatedProject = $project | Invoke-DatabaseBuild -TemporaryDatabaseServer "Data Source=temp01\sql2014"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify a SQL Server instance for the temporary database, instead of using LocalDB.</maml:para>
          <maml:para>This is useful if your database uses features that aren't supported by LocalDB, such as Full-Text Search.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 4 ----------</maml:title>
        <dev:code>$project = "C:\Work\project\project.sqlproj"
$temporaryDatabase = New-DatabaseConnection -ServerInstance "temp01\sql2014" -Database "TemporaryDb"
$validatedProject = $project | Invoke-DatabaseBuild -TemporaryDatabase $temporaryDatabase</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify an existing SQL Server database to be used when building a project.</maml:para>
          <maml:para>This is useful if you don't want to use LocalDB and you don't have permission to create a database on the SQL Server instance.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 5 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$options = "IgnoreComments, AddObjectExistenceChecks, -IgnoreUserProperties"
$validatedProject = $project | Invoke-DatabaseBuild -SQLCompareOptions $options</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify SQL Compare options to be used when building a SQL Source Control project.</maml:para>
          <maml:para>The $options variable is used to specify that the IgnoreComments and AddObjectExistenceChecks options should be included in addition to the default set of SQL Compare options used by this cmdlet. The minus sign before IgnoreUserProperties indicates that this default option will be turned off.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Export-DatabaseBuildArtifact -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Export-DatabaseBuildArtifact</command:name>
      <command:verb>Export</command:verb>
      <command:noun>DatabaseBuildArtifact</command:noun>
      <maml:description>
        <maml:para>Exports an IBuildArtifact object to disk.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Export-DatabaseBuildArtifact cmdlet exports the IBuildArtifact object produced by the New-DatabaseBuildArtifact cmdlet as a NuGet package or as a .zip file.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Export-DatabaseBuildArtifact</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The IBuildArtifact object to be exported.</maml:para>
          </maml:description>
          <command:parameterValue required="true">IBuildArtifact</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Path -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Path</maml:name>
          <maml:description>
            <maml:para>The path to the folder the build artifact is exported to. If the folder doesn't already exist, it will be created when the build artifact is exported.</maml:para>
          </maml:description>
          <command:parameterValue required="true">object</command:parameterValue>
          <dev:type>
            <maml:name>System.Object</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Force -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Force</maml:name>
          <maml:description>
            <maml:para>Use this parameter to overwrite any existing build artifact with the same name.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: OutputFormat -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>OutputFormat</maml:name>
          <maml:description>
            <maml:para>The output format of the Build Artifact. If you don't use this parameter the default behaviour is to export to a NuGet package</maml:para>
            <maml:para>Possible values: NuGet, Zip</maml:para>
          </maml:description>
          <command:parameterValue required="true">BuildArtifactOutputFormat</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.BuildArtifacts.BuildArtifactOutputFormat</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>NuGet</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">NuGet</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Zip</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The IBuildArtifact object to be exported.</maml:para>
        </maml:description>
        <command:parameterValue required="true">IBuildArtifact</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Path -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>Path</maml:name>
        <maml:description>
          <maml:para>The path to the folder the build artifact is exported to. If the folder doesn't already exist, it will be created when the build artifact is exported.</maml:para>
        </maml:description>
        <command:parameterValue required="true">object</command:parameterValue>
        <dev:type>
          <maml:name>System.Object</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Force -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Force</maml:name>
        <maml:description>
          <maml:para>Use this parameter to overwrite any existing build artifact with the same name.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: OutputFormat -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>OutputFormat</maml:name>
        <maml:description>
          <maml:para>The output format of the Build Artifact. If you don't use this parameter the default behaviour is to export to a NuGet package</maml:para>
          <maml:para>Possible values: NuGet, Zip</maml:para>
        </maml:description>
        <command:parameterValue required="true">BuildArtifactOutputFormat</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.BuildArtifacts.BuildArtifactOutputFormat</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>NuGet</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">NuGet</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Zip</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The IBuildArtifact object to be exported.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: None -->
      <command:returnValue>
        <dev:type>
          <maml:name>None</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$project = "C:\Work\project\project.sqlproj"
$validatedProject = $project | Invoke-DatabaseBuild
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0
$buildArtifact | Export-DatabaseBuildArtifact -Path "C:\Export\buildArtifacts"</dev:code>
        <dev:remarks>
          <maml:para>In this example, the New-DatabaseBuildArtifact cmdlet creates an IBuildArtifact object from a validated database schema. The Export-DatabaseBuildArtifact cmdlet then exports the build artifact to C:\Export\buildArtifacts as a NuGet package.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$project = "C:\Work\project\project.sqlproj"
$validatedProject = $project | Invoke-DatabaseBuild
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0
$buildArtifact | Export-DatabaseBuildArtifact -Path "C:\Export\buildArtifacts" -OutputFormat Zip</dev:code>
        <dev:remarks>
          <maml:para>In this example, the New-DatabaseBuildArtifact cmdlet creates an IBuildArtifact object from a validated database schema. The Export-DatabaseBuildArtifact cmdlet then exports the build artifact to C:\Export\buildArtifacts as a zip file.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$scriptsFolder = "C:\Work\scripts"
$validatedProject = $scriptsFolder | Invoke-DatabaseBuild
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0
$buildArtifact | Export-DatabaseBuildArtifact -Path "C:\Export\buildArtifacts"</dev:code>
        <dev:remarks>
          <maml:para>In this example, the New-DatabaseBuildArtifact cmdlet creates an IBuildArtifact object from a validated database schema. The Export-DatabaseBuildArtifact cmdlet then exports the package to c:\Export\buildArtifacts as a NuGet package.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Import-DatabaseBuildArtifact -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Import-DatabaseBuildArtifact</command:name>
      <command:verb>Import</command:verb>
      <command:noun>DatabaseBuildArtifact</command:noun>
      <maml:description>
        <maml:para>Imports a build artifact to an instance of an IBuildArtifact object.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Import-DatabaseBuildArtifact cmdlet uses an on disk build artifact to create a IBuildArtifact object that can be used as the input for other cmdlets such as Publish-DatabaseBuildArtifact.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Import-DatabaseBuildArtifact</maml:name>
        <!-- Parameter: Path -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>Path</maml:name>
          <maml:description>
            <maml:para>The path to the build artifact file (eg 'C:\Work\buildArtifacts\MyDatabase.1.0.0.nupkg').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: Path -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>Path</maml:name>
        <maml:description>
          <maml:para>The path to the build artifact file (eg 'C:\Work\buildArtifacts\MyDatabase.1.0.0.nupkg').</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The path to the build artifact file (eg 'C:\Work\buildArtifacts\MyDatabase.1.0.0.nupkg').</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: IBuildArtifact -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$buildArtifactPath = "C:\Work\buildArtifacts\MyDatabase.1.0.0.nupkg"
$buildArtifact = $buildArtifactPath | Import-DatabaseBuildArtifact
$buildArtifact | Publish-DatabaseBuildArtifact -NuGetFeedUrl http://localhost:4000/nuget/packages -NuGetApiKey ed6d7c98-9847-4599-b5a8-323f215b5c89</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Import-DatabaseBuildArtifact cmdlet to create a IBuildArtifact object from a build artifact exported as NuGet package. The Publish-DatabaseBuildArtifact cmdlet then publishes the output object to a NuGet feed.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$buildArtifactPath = "C:\Work\buildArtifacts\MyDatabase.zip"
$buildArtifact = $buildArtifactPath | Import-DatabaseBuildArtifact</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Import-DatabaseBuildArtifact cmdlet to create a IBuildArtifact object from a build artifact exported as a .zip file.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: New-DatabaseBuildArtifact -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>New-DatabaseBuildArtifact</command:name>
      <command:verb>New</command:verb>
      <command:noun>DatabaseBuildArtifact</command:noun>
      <maml:description>
        <maml:para>Creates a build artifact from the validated project produced by the Invoke-DatabaseBuild cmdlet.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The New-DatabaseBuildArtifact cmdlet takes a validated project from the output of the Invoke-DatabaseBuild cmdlet and creates a build artifact. It can also include the documentation for your database using the output of the New-DatabaseDocumentation cmdlet.</maml:para>
      <maml:para>You can use the Export-DatabaseBuildArtifact cmdlet to export the build artifact.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>New-DatabaseBuildArtifact</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The output object of Invoke-DatabaseBuild cmdlet, which represents the validated project.</maml:para>
          </maml:description>
          <command:parameterValue required="true">IProject</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: PackageId -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>PackageId</maml:name>
          <maml:description>
            <maml:para>The unique identifier for the package you are creating.</maml:para>
            <maml:para>This mustn't contain more than 100 characters and must be a valid NuGet package identifier.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: PackageVersion -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>PackageVersion</maml:name>
          <maml:description>
            <maml:para>The version of the package. This must be in a valid NuGet version format (eg 3.2.1, 3.2.1-beta1).</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Documentation -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Documentation</maml:name>
          <maml:description>
            <maml:para>The documentation object created by New-DatabaseDocumentation to include in the database package.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SchemaDocumentation</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Documentation.SchemaDocumentation</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: PackageDescription -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>PackageDescription</maml:name>
          <maml:description>
            <maml:para>The description of the package you are creating.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The output object of Invoke-DatabaseBuild cmdlet, which represents the validated project.</maml:para>
        </maml:description>
        <command:parameterValue required="true">IProject</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: PackageId -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>PackageId</maml:name>
        <maml:description>
          <maml:para>The unique identifier for the package you are creating.</maml:para>
          <maml:para>This mustn't contain more than 100 characters and must be a valid NuGet package identifier.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: PackageVersion -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>PackageVersion</maml:name>
        <maml:description>
          <maml:para>The version of the package. This must be in a valid NuGet version format (eg 3.2.1, 3.2.1-beta1).</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: PackageDescription -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>PackageDescription</maml:name>
        <maml:description>
          <maml:para>The description of the package you are creating.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Documentation -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Documentation</maml:name>
        <maml:description>
          <maml:para>The documentation object created by New-DatabaseDocumentation to include in the database package.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SchemaDocumentation</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Documentation.SchemaDocumentation</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The output object of Invoke-DatabaseBuild cmdlet, which represents the validated project.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: IBuildArtifact -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$project = "C:\Work\project\project.sqlproj"
$validatedProject = $project | Invoke-DatabaseBuild
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0
$buildArtifact | Export-DatabaseBuildArtifact -Path "C:\Export\buildArtifacts"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the New-DatabaseBuildArtifact cmdlet to create a build artifact from a validated SQL Change Automation project.</maml:para>
          <maml:para>First the Invoke-DatabaseBuild cmdlet validates the project. Then the New-DatabaseBuildArtifact cmdlet creates the build artifact. Finally the Export-DatabaseBuildArtifact cmdlet exports the build artifact to file.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$validatedProject = $project | Invoke-DatabaseBuild
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0
$buildArtifact | Export-DatabaseBuildArtifact -Path "C:\Export\buildArtifacts"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the New-DatabaseBuildArtifact cmdlet to create a NuGet package from a validated SQL Source Control project.</maml:para>
          <maml:para>First the Invoke-DatabaseBuild cmdlet validates the database schema. Then the New-DatabaseBuildArtifact cmdlet creates the build artifact. Finally the Export-DatabaseBuildArtifact cmdlet exports the build artifact to file.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$validatedProject = $project | Invoke-DatabaseBuild
$documentation = $validatedProject | New-DatabaseDocumentation
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0 -Documentation $documentation
$buildArtifact | Export-DatabaseBuildArtifact -Path "C:\Export\buildArtifacts"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the New-DatabaseBuildArtifact cmdlet to create a NuGet build artifact that also includes database documentation.</maml:para>
          <maml:para>The documentation is created by the New-DatabaseDocumentation cmdlet.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Publish-DatabaseBuildArtifact -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Publish-DatabaseBuildArtifact</command:name>
      <command:verb>Publish</command:verb>
      <command:noun>DatabaseBuildArtifact</command:noun>
      <maml:description>
        <maml:para>Publishes a database build artifact to a NuGet feed or to DLM Dashboard.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Publish-DatabaseBuildArtifact cmdlet publishes an IBuildArtifact object produced by the New-DatabaseBuildArtifact cmdlet to a specified NuGet feed or to DLM Dashboard.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: NuGet -->
      <command:syntaxItem>
        <maml:name>Publish-DatabaseBuildArtifact</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>An instance of a IBuildArtifact object to be published.</maml:para>
            <maml:para>This object is produced by the New-DatabaseBuildArtifact and Import-DatabaseBuildArtifact cmdlets.</maml:para>
          </maml:description>
          <command:parameterValue required="true">IBuildArtifact</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: NuGetFeedUrl -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>NuGetFeedUrl</maml:name>
          <maml:description>
            <maml:para>The NuGet feed that the database build artifact will be published to.</maml:para>
            <maml:para>This must be valid URL for a NuGet feed.</maml:para>
            <maml:para>You can't use this parameter in addition to the DlmDashboardUrl parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: NuGetApiKey -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>NuGetApiKey</maml:name>
          <maml:description>
            <maml:para>The API key for the NuGet server.</maml:para>
            <maml:para>You can't use this parameter in addition to the DlmDashboardUrl parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
      <!-- Parameter set: DLMDashboard -->
      <command:syntaxItem>
        <maml:name>Publish-DatabaseBuildArtifact</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>An instance of a IBuildArtifact object to be published.</maml:para>
            <maml:para>This object is produced by the New-DatabaseBuildArtifact and Import-DatabaseBuildArtifact cmdlets.</maml:para>
          </maml:description>
          <command:parameterValue required="true">IBuildArtifact</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: DlmDashboardUrl -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>DlmDashboardUrl</maml:name>
          <maml:description>
            <maml:para>The URL, including port number, to the instance of DLM Dashboard that the database build artifact will be published to.</maml:para>
            <maml:para>You can't use this parameter in addition to the NuGetFeedUrl and NuGetApiKey parameters.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>An instance of a IBuildArtifact object to be published.</maml:para>
          <maml:para>This object is produced by the New-DatabaseBuildArtifact and Import-DatabaseBuildArtifact cmdlets.</maml:para>
        </maml:description>
        <command:parameterValue required="true">IBuildArtifact</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: NuGetFeedUrl -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>NuGetFeedUrl</maml:name>
        <maml:description>
          <maml:para>The NuGet feed that the database build artifact will be published to.</maml:para>
          <maml:para>This must be valid URL for a NuGet feed.</maml:para>
          <maml:para>You can't use this parameter in addition to the DlmDashboardUrl parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: NuGetApiKey -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>NuGetApiKey</maml:name>
        <maml:description>
          <maml:para>The API key for the NuGet server.</maml:para>
          <maml:para>You can't use this parameter in addition to the DlmDashboardUrl parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: DlmDashboardUrl -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>DlmDashboardUrl</maml:name>
        <maml:description>
          <maml:para>The URL, including port number, to the instance of DLM Dashboard that the database build artifact will be published to.</maml:para>
          <maml:para>You can't use this parameter in addition to the NuGetFeedUrl and NuGetApiKey parameters.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.BuildArtifacts.IBuildArtifact</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>An instance of a IBuildArtifact object to be published.</maml:para>
          <maml:para>This object is produced by the New-DatabaseBuildArtifact and Import-DatabaseBuildArtifact cmdlets.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: None -->
      <command:returnValue>
        <dev:type>
          <maml:name>None</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$scriptsFolder = "C:\Work\scripts"
$validatedProject = $scriptsFolder | Invoke-DatabaseBuild
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0
$buildArtifact | Publish-DatabaseBuildArtifact -NuGetFeedUrl http://localhost:4000/nuget/packages -NuGetApiKey ed6d7c98-9847-4599-b5a8-323f215b5c89</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Publish-DatabaseBuildArtifact cmdlet to publish a build artifact object produced by the New-DatabaseBuildArtifact cmdlet to a NuGet feed.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$buildArtifactPath = "c:\Work\buildArtifacts\MyDatabase.1.0.0.nupkg"
$buildArtifact = $buildArtifactPath | Import-DatabaseBuildArtifact
$buildArtifact | Publish-DatabaseBuildArtifact -NuGetFeedUrl http://localhost:4000/nuget/packages -NuGetApiKey ed6d7c98-9847-4599-b5a8-323f215b5c89</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to publish a database build artifact file to a NuGet feed. The Import-DatabaseBuildArtifact cmdlet creates an instance of an IBuildArtifact object, which is then used as the input for the Publish-DatabaseBuildArtifact cmdlet.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$scriptsFolder = "C:\Work\scripts"
$validatedProject = $scriptsFolder | Invoke-DatabaseBuild
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0
$buildArtifact | Publish-DatabaseBuildArtifact -DlmDashboardUrl http://localhost:19528</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Publish-DatabaseBuildArtifact cmdlet to publish a database build artifact object to DLM Dashboard.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: New-DatabaseConnection -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>New-DatabaseConnection</command:name>
      <command:verb>New</command:verb>
      <command:noun>DatabaseConnection</command:noun>
      <maml:description>
        <maml:para>Creates an object that other SQL Change Automation cmdlets can use to connect to a database.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The New-DatabaseConnection cmdlet creates a DatabaseConnection object that can be used by other SQL Change Automation cmdlets to connect to a database. The object contains the server instance, database name, and security credentials that cmdlets will use to connect to the database.</maml:para>
      <maml:para>You can use Windows authentication or SQL Server authentication to connect to the database. If you use the Username and Password parameters, SQL Server authentication will be used. If you don't use those parameters, Windows authentication will be used; the account used to connect will be the account running PowerShell or the PowerShell script.</maml:para>
      <maml:para>The cmdlets that can use the Database Connection object to connect to a database are Invoke-DatabaseBuild, New-DatabaseReleaseArtifact, Sync-DatabaseSchema, Test-DatabaseConnection and Use-DatabaseReleaseArtifact.</maml:para>
      <maml:para>As an alternative to using this cmdlet, you may use a standard database connection string in place of a Database Connection object. The following connection string properties are supported: ApplicationIntent, Asynchronous Processing, AttachDbFilename, Connect Timeout, Context Connection, Current Language, Data Source, Encrypt, Enlist, Failover Partner, Initial Catalog, Integrated Security, Load Balance Timeout, Max Pool Size, Min Pool Size, MultipleActiveResultSets, MultiSubnetFailover, Network Library, Packet Size, Password, Persist Security Info, Replication, Transaction Binding, TrustServerCertificate, Type System Version, User ID, User Instance and Workstation ID.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>New-DatabaseConnection</maml:name>
        <!-- Parameter: Database -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Database</maml:name>
          <maml:description>
            <maml:para>The database to connect to, on the server specified in ServerInstance. This is equivalent to the Initial Catalog property of a connection string.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: ServerInstance -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>ServerInstance</maml:name>
          <maml:description>
            <maml:para>The name or network address of the SQL Server instance to connect to. For example, "staging01\sql2014". This is equivalent to the Data Source property of a connection string.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Authentication -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Authentication</maml:name>
          <maml:description>
            <maml:para>The authentication method that will be used to connect to the server. Possible values are "IntegratedSecurity", "SqlAuthentication" or "ActiveDirectoryPassword". This parameter is optional. If this parameter is not specified, SqlAuthentication will be used if a username is provided, otherwise IntegratedSecurity will be used.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Encrypt -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Encrypt</maml:name>
          <maml:description>
            <maml:para>Indicates if the connection should be encrypted using SSL. This parameter is optional. If left unspecified it defaults to false.</maml:para>
          </maml:description>
          <command:parameterValue required="true">bool</command:parameterValue>
          <dev:type>
            <maml:name>System.Boolean</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: Password -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Password</maml:name>
          <maml:description>
            <maml:para>The password for the SQL Server account cmdlets will use to connect to the database. This is equivalent to the Password property of a connection string. This parameter is optional. If left unspecified, it defaults to the empty string.</maml:para>
            <maml:para>This parameter is ignored if the Username parameter is null or empty.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TrustServerCertificate -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TrustServerCertificate</maml:name>
          <maml:description>
            <maml:para>Indicates if the server certificate should be verified when connecting using SSL encryption. In order to provide backwards compatibility, if this parameter is set to false then it may still be promoted to true if the target server connection is local under some circumstances. This parameter is optional. If left unspecified it defaults to false.</maml:para>
          </maml:description>
          <command:parameterValue required="true">bool</command:parameterValue>
          <dev:type>
            <maml:name>System.Boolean</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: Username -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Username</maml:name>
          <maml:description>
            <maml:para>The username for the SQL Server account cmdlets will use to connect to the database. This is equivalent to the User ID property of a connection string. This parameter is optional. If you specify a null or empty string, Windows Authentication will be used and the Password parameter will be ignored.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: ServerInstance -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>ServerInstance</maml:name>
        <maml:description>
          <maml:para>The name or network address of the SQL Server instance to connect to. For example, "staging01\sql2014". This is equivalent to the Data Source property of a connection string.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Database -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>Database</maml:name>
        <maml:description>
          <maml:para>The database to connect to, on the server specified in ServerInstance. This is equivalent to the Initial Catalog property of a connection string.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Authentication -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Authentication</maml:name>
        <maml:description>
          <maml:para>The authentication method that will be used to connect to the server. Possible values are "IntegratedSecurity", "SqlAuthentication" or "ActiveDirectoryPassword". This parameter is optional. If this parameter is not specified, SqlAuthentication will be used if a username is provided, otherwise IntegratedSecurity will be used.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Username -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Username</maml:name>
        <maml:description>
          <maml:para>The username for the SQL Server account cmdlets will use to connect to the database. This is equivalent to the User ID property of a connection string. This parameter is optional. If you specify a null or empty string, Windows Authentication will be used and the Password parameter will be ignored.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Password -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Password</maml:name>
        <maml:description>
          <maml:para>The password for the SQL Server account cmdlets will use to connect to the database. This is equivalent to the Password property of a connection string. This parameter is optional. If left unspecified, it defaults to the empty string.</maml:para>
          <maml:para>This parameter is ignored if the Username parameter is null or empty.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TrustServerCertificate -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TrustServerCertificate</maml:name>
        <maml:description>
          <maml:para>Indicates if the server certificate should be verified when connecting using SSL encryption. In order to provide backwards compatibility, if this parameter is set to false then it may still be promoted to true if the target server connection is local under some circumstances. This parameter is optional. If left unspecified it defaults to false.</maml:para>
        </maml:description>
        <command:parameterValue required="true">bool</command:parameterValue>
        <dev:type>
          <maml:name>System.Boolean</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: Encrypt -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Encrypt</maml:name>
        <maml:description>
          <maml:para>Indicates if the connection should be encrypted using SSL. This parameter is optional. If left unspecified it defaults to false.</maml:para>
        </maml:description>
        <command:parameterValue required="true">bool</command:parameterValue>
        <dev:type>
          <maml:name>System.Boolean</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
    </command:parameters>
    <command:inputTypes />
    <command:returnValues>
      <!-- OutputType: DatabaseConnection -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging" -Username "AutomationUser" -Password "P@ssw0rd"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to create a Database Connection object. The object will use SQL Server authentication to connect to the database.</maml:para>
          <maml:para>The New-DatabaseConnection cmdlet creates a Database Connection object, $staging. This can be used to connect to the database, Staging, on the SQL Server staging01\sql2014. Because the Username and Password parameters are provided, SQL Server authentication will be used to connect to Staging.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to create a Database Connection object that will use Windows authentication to connect to the database.</maml:para>
          <maml:para>The New-DatabaseConnection cmdlet creates a Database Connection object, $staging. This can be used to connect to the database Staging on the SQL Server staging01\sql2014. Because no Username and Password are provided, Windows authentication will be used to connect to the database.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Test-DatabaseConnection -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Test-DatabaseConnection</command:name>
      <command:verb>Test</command:verb>
      <command:noun>DatabaseConnection</command:noun>
      <maml:description>
        <maml:para>Checks a DatabaseConnection object can connect to the database.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Test-DatabaseConnection cmdlet checks that the details in a DatabaseConnection object produced by the New-DatabaseConnection cmdlet can be used to connect to the specified database.</maml:para>
      <maml:para>If Test-DatabaseConnection can't connect to the database, it raises an error.</maml:para>
      <maml:para>After testing the connection, the cmdlet pipes out the input DatabaseConnection object. This allows you to use Test-DatabaseConnection in a chain of cmdlets.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Test-DatabaseConnection</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The Database Connection object or database connection string that identifies the connection to test. See New-DatabaseConnection for details.</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The Database Connection object or database connection string that identifies the connection to test. See New-DatabaseConnection for details.</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The Database Connection object or database connection string that identifies the connection to test. See New-DatabaseConnection for details.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: DatabaseConnection -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$connection = New-DatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production" -Username "AutomationUser" -Password "P@ssw0rd"
Test-DatabaseConnection $connection</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Test-DatabaseConnection cmdlet to check that a Database Connection object can connect to a database.</maml:para>
          <maml:para>The New-DatabaseConnection cmdlet creates a Database Connection object, $connection. This contains the details needed to connect to the database, Production, on prod01\sql2014. The Test-DatabaseConnection cmdlet then checks these details can be used to connect to Production.</maml:para>
          <maml:para>If Test-DatabaseConnection can't connect to the database, you must check the connection details, and create a new Database Connection object with the correct details.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$connection = New-DatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production" -Username "AutomationUser" -Password "P@ssw0rd" | Test-DatabaseConnection</dev:code>
        <dev:remarks>
          <maml:para>This example show how to pass a Database Connection object through the pipeline to the Test-DatabaseConnection cmdlet.</maml:para>
          <maml:para>The New-DatabaseConnection cmdlet creates a Database Connection object. This is piped to the Test-DatabaseConnection cmdlet.</maml:para>
          <maml:para>Test-DatabaseConnection checks that it can connect to the database, Production, using the Database Connection object. It then pipes the same Database Connection object out. This allows it to be assigned to the $connection variable.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: New-DatabaseDocumentation -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>New-DatabaseDocumentation</command:name>
      <command:verb>New</command:verb>
      <command:noun>DatabaseDocumentation</command:noun>
      <maml:description>
        <maml:para>Generates documentation for the validated database schema produced by the Invoke-DlmDatabaseValidation cmdlet.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The New-DatabaseDocumentation cmdlet takes the output of the Invoke-DatabaseBuild cmdlet and creates documentation for that schema. It creates a SchemaDocumentation object that represents the documentation for a validated project.</maml:para>
      <maml:para>You can use the New-DatabaseBuildArtifact cmdlet to include this documentation in the database build artifact it creates.</maml:para>
      <maml:para>In order to generate the documentation, the cmdlet creates a temporary copy of the database. By default, it uses LocalDB for this. Alternatively, you can use the TemporaryDatabaseServer parameter to specify a SQL Server instance for the temporary database. This is useful if your database uses features that aren't supported by LocalDB, such as Full-Text Search.</maml:para>
      <maml:para>If you don't want to use LocalDB but don't have permission to create a database on the SQL Server instance, you can use the TemporaryDatabase parameter to specify an existing database.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: TemporaryDatabaseServer -->
      <command:syntaxItem>
        <maml:name>New-DatabaseDocumentation</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The output object of Invoke-DatabaseBuild cmdlet, which represents the validated database schema.</maml:para>
          </maml:description>
          <command:parameterValue required="true">IProject</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when documenting this schema.</maml:para>
            <maml:para>This parameter will be ignored if the value specified is either $null or empty.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>Whether the SQL Compare engine should ignore parser errors.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when creating the script for validation. A default set of options is listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TemporaryDatabaseServer -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TemporaryDatabaseServer</maml:name>
          <maml:description>
            <maml:para>The connection string for the temporary database server used for documentation. For example, 'Data Source=TempServer01'.</maml:para>
            <maml:para>By default, LocalDB is used for the temporary database. However there may be some features in your database that aren't supported by LocalDB (for example, Full-Text Search). In this case, or if LocalDB is not present, use this parameter to specify an alternative SQL Server instance for the temporary database.</maml:para>
            <maml:para>Using this option, SQL Change Automation will create a temporary, randomly-named database on the specified SQL Server instance.</maml:para>
            <maml:para>You can't use this parameter in addition to the TemporaryDatabase parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseServerConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseServerConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
      <!-- Parameter set: TemporaryDatabase -->
      <command:syntaxItem>
        <maml:name>New-DatabaseDocumentation</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The output object of Invoke-DatabaseBuild cmdlet, which represents the validated database schema.</maml:para>
          </maml:description>
          <command:parameterValue required="true">IProject</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when documenting this schema.</maml:para>
            <maml:para>This parameter will be ignored if the value specified is either $null or empty.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>Whether the SQL Compare engine should ignore parser errors.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when creating the script for validation. A default set of options is listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TemporaryDatabase -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TemporaryDatabase</maml:name>
          <maml:description>
            <maml:para>The details of the temporary database used for documentation. This can be:</maml:para>
            <maml:para>- a database connection object that contains connection details for a database. See New-DatabaseConnection for details.</maml:para>
            <maml:para>- a database connection string. For example, 'Data Source=TempServer01;Initial Catalog=TempDatabase01'.</maml:para>
            <maml:para>By default, LocalDB is used for the temporary database. If you don't want to use LocalDB and don't have permission to create a database on the SQL Server instance, use this option to specify an existing database to use for the temporary copy of the database.</maml:para>
            <maml:para>If you use this parameter, all existing data on the temporary database will be lost.</maml:para>
            <maml:para>You can't use this parameter in addition to the TemporaryDatabaseServer parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The output object of Invoke-DatabaseBuild cmdlet, which represents the validated database schema.</maml:para>
        </maml:description>
        <command:parameterValue required="true">IProject</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TemporaryDatabaseServer -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TemporaryDatabaseServer</maml:name>
        <maml:description>
          <maml:para>The connection string for the temporary database server used for documentation. For example, 'Data Source=TempServer01'.</maml:para>
          <maml:para>By default, LocalDB is used for the temporary database. However there may be some features in your database that aren't supported by LocalDB (for example, Full-Text Search). In this case, or if LocalDB is not present, use this parameter to specify an alternative SQL Server instance for the temporary database.</maml:para>
          <maml:para>Using this option, SQL Change Automation will create a temporary, randomly-named database on the specified SQL Server instance.</maml:para>
          <maml:para>You can't use this parameter in addition to the TemporaryDatabase parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseServerConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseServerConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TemporaryDatabase -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TemporaryDatabase</maml:name>
        <maml:description>
          <maml:para>The details of the temporary database used for documentation. This can be:</maml:para>
          <maml:para>- a database connection object that contains connection details for a database. See New-DatabaseConnection for details.</maml:para>
          <maml:para>- a database connection string. For example, 'Data Source=TempServer01;Initial Catalog=TempDatabase01'.</maml:para>
          <maml:para>By default, LocalDB is used for the temporary database. If you don't want to use LocalDB and don't have permission to create a database on the SQL Server instance, use this option to specify an existing database to use for the temporary copy of the database.</maml:para>
          <maml:para>If you use this parameter, all existing data on the temporary database will be lost.</maml:para>
          <maml:para>You can't use this parameter in addition to the TemporaryDatabaseServer parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: FilterPath -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>FilterPath</maml:name>
        <maml:description>
          <maml:para>The path to a .scpf filter file.</maml:para>
          <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when documenting this schema.</maml:para>
          <maml:para>This parameter will be ignored if the value specified is either $null or empty.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: IgnoreParserErrors -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreParserErrors</maml:name>
        <maml:description>
          <maml:para>Whether the SQL Compare engine should ignore parser errors.</maml:para>
          <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: SQLCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Compare options to use when creating the script for validation. A default set of options is listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
          <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
          <maml:para>By default, the following Compare options are used:</maml:para>
          <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
          <maml:para>- DecryptEncryptedObjects</maml:para>
          <maml:para>- DoNotOutputCommentHeader</maml:para>
          <maml:para>- ForceColumnOrder</maml:para>
          <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
          <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
          <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
          <maml:para>- IgnoreUserProperties</maml:para>
          <maml:para>- IgnoreWhiteSpace</maml:para>
          <maml:para>- IgnoreWithElementOrder</maml:para>
          <maml:para>- IncludeDependencies</maml:para>
          <maml:para>- ThrowOnFileParseFailed</maml:para>
          <maml:para>- UseCompatibilityLevel</maml:para>
          <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: SQLDataCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLDataCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The output object of Invoke-DatabaseBuild cmdlet, which represents the validated database schema.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: SchemaDocumentation -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Documentation.SchemaDocumentation</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$project = "C:\Work\project\project.sqlproj"
$validatedProject = $project | Invoke-DatabaseBuild
$documentation = $validatedProject | New-DatabaseDocumentation
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0 -Documentation $documentation</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to create database documentation for a validated SQL Change Automation project using the New-DatabaseDocumentation cmdlet. The New-DatabaseBuildArtifact cmdlet includes this documentation in the database build artifact it creates.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$scriptsFolder = "C:\Work\scripts"
$validatedProject = $scriptsFolder | Invoke-DatabaseBuild
$documentation = $validatedProject | New-DatabaseDocumentation
$buildArtifact = $validatedProject | New-DatabaseBuildArtifact -PackageId MyDatabase -PackageVersion 1.0.0 -Documentation $documentation</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to create database documentation for a validated SQL Source Control project using the New-DatabaseDocumentation cmdlet. The New-DatabaseBuildArtifact cmdlet includes this documentation in the database build artifact it creates.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: New-DatabaseProjectObject -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>New-DatabaseProjectObject</command:name>
      <command:verb>New</command:verb>
      <command:noun>DatabaseProjectObject</command:noun>
      <maml:description>
        <maml:para>Creates an IProject from a path.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The New-DatabaseProjectObject cmdlet takes a path and creates an IProject object that represents the project.</maml:para>
      <maml:para>The cmdlet assumes you have built the project by other means and does not attempt to perform its own build.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>New-DatabaseProjectObject</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The path to the database project.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The path to the database project.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The path to the database project.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: IProject -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.Projects.IProject</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$projectPath = "C:\Work\scripts"
$project = $projectPath | New-DatabaseProjectObject</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the New-DatabaseProjectObject cmdlet to obtain an IProject from a SQL Source Control Project which can be used to create a build artifact.</maml:para>
          <maml:para>It is recommended to use Invoke-DatabaseBuild instead if you are able to - this cmdlet does not guarantee your project is actually valid, and your process may fail unexpectedly later if it is not. Please only use this cmdlet if you are certain that the changes you have made are applicable. This cmdlet will output an instance of a IProject object that can be used as the input for other SQL Change Automation cmdlets.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$projectPath = "C:\Work\project\project.sqlproj"
$project = $projectPath | New-DatabaseProjectObject</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the New-DatabaseProjectObject cmdlet to obtain an IProject from a SQL Change Automation Project which can be used to create a build artifact.</maml:para>
          <maml:para>It is recommended to use Invoke-DatabaseBuild instead if you are able to - this cmdlet does not guarantee your project is actually valid, and your process may fail unexpectedly later if it is not. Please only use this cmdlet if you are certain that the changes you have made are applicable. This cmdlet will output an instance of a IProject object that can be used as the input for other SQL Change Automation cmdlets.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Export-DatabaseReleaseArtifact -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Export-DatabaseReleaseArtifact</command:name>
      <command:verb>Export</command:verb>
      <command:noun>DatabaseReleaseArtifact</command:noun>
      <maml:description>
        <maml:para>Exports a Release Artifact produced by the New-DatabaseReleaseArtifact cmdlet to a folder or .zip file on disk.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Export-DatabaseReleaseArtifact cmdlet exports database deployment resources, which are produced by the New-DatabaseReleaseArtifact cmdlet to a folder or .zip file.</maml:para>
      <maml:para>Specify the output folder or file using the Path parameter. If the Path ends in .zip, the database deployment resources will be exported to a .zip file. Otherwise, they'll be exported to a folder. You can override this choice with the optional Format parameter.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Export-DatabaseReleaseArtifact</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The IReleaseArtifact object to be exported.</maml:para>
          </maml:description>
          <command:parameterValue required="true">IReleaseArtifact</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Domain.ReleaseArtifacts.IReleaseArtifact</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Path -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Path</maml:name>
          <maml:description>
            <maml:para>The path to the output folder or .zip file. If the path ends in ".zip", the Database Release is exported to a zip file. Otherwise it is exported to a folder. You can override this automatic choice using the Format parameter, and setting it to either "Zip" or "Folder" as required.</maml:para>
          </maml:description>
          <command:parameterValue required="true">object</command:parameterValue>
          <dev:type>
            <maml:name>System.Object</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Force -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Force</maml:name>
          <maml:description>
            <maml:para>Indicates that any existing output file or folder should be overwritten.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: Format -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Format</maml:name>
          <maml:description>
            <maml:para>The output format of the Database Release. If you specify Zip, the Database Release will be exported to a .zip file. If you specify Folder, the Database Release will be exported to a folder. If you specify Default or don't use the parameter, the output format will be determined by the Path parameter.</maml:para>
            <maml:para>Possible values: Default, Folder, Zip</maml:para>
          </maml:description>
          <command:parameterValue required="true">OutputFormat</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Import.OutputFormat</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>Default</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Default</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Folder</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Zip</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The IReleaseArtifact object to be exported.</maml:para>
        </maml:description>
        <command:parameterValue required="true">IReleaseArtifact</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.ReleaseArtifacts.IReleaseArtifact</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Path -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>Path</maml:name>
        <maml:description>
          <maml:para>The path to the output folder or .zip file. If the path ends in ".zip", the Database Release is exported to a zip file. Otherwise it is exported to a folder. You can override this automatic choice using the Format parameter, and setting it to either "Zip" or "Folder" as required.</maml:para>
        </maml:description>
        <command:parameterValue required="true">object</command:parameterValue>
        <dev:type>
          <maml:name>System.Object</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Format -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Format</maml:name>
        <maml:description>
          <maml:para>The output format of the Database Release. If you specify Zip, the Database Release will be exported to a .zip file. If you specify Folder, the Database Release will be exported to a folder. If you specify Default or don't use the parameter, the output format will be determined by the Path parameter.</maml:para>
          <maml:para>Possible values: Default, Folder, Zip</maml:para>
        </maml:description>
        <command:parameterValue required="true">OutputFormat</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Import.OutputFormat</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>Default</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Default</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Folder</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Zip</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
      <!-- Parameter: Force -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Force</maml:name>
        <maml:description>
          <maml:para>Indicates that any existing output file or folder should be overwritten.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.ReleaseArtifacts.IReleaseArtifact</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The IReleaseArtifact object to be exported.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: None -->
      <command:returnValue>
        <dev:type>
          <maml:name>None</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$production = New-DatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production"
$build = Import-DatabaseBuildArtifact "C:\Work\buildArtifacts\DatabaseBuildArtifact.1.0.0.nupkg"
 
$release = New-DatabaseReleaseArtifact -Source $build -Target $production
$release | Export-DatabaseReleaseArtifact -Path "C:\Export\DatabaseRelease"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to create a SQL Change Automation Release Artifact and export it to a folder.</maml:para>
          <maml:para>The New-DatabaseReleaseArtifact cmdlet creates a IReleaseArtifact object, which represents the database deployment resources. This object can update the database, Production. The IReleaseArtifact object is passed through the pipeline to the Export-DatabaseReleaseArtifact cmdlet. This cmdlet exports the database deployment resources to the folder C:\Export\DatabaseRelease\. The resources are exported to a folder because the Path parameter didn't end in .zip.</maml:para>
          <maml:para>Exporting database deployment resources lets you review the update script and other update resources, such as the change report and deployment warnings.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$production = New-DatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production"
$build = Import-DatabaseBuildArtifact "C:\Work\buildArtifacts\DatabaseBuildArtifact.1.0.0.nupkg"
 
$release = New-DatabaseReleaseArtifact -Source $build -Target $production
$release | Export-DatabaseReleaseArtifact -Path "C:\Export\DatabaseRelease.zip"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to create a database deployment resources and export it to a .zip file.</maml:para>
          <maml:para>The New-DatabaseReleaseArtifact cmdlet creates an IReleaseArtifact object, representing the database deployment resources, which is passed through the pipeline to the Export-DatabaseReleaseArtifact cmdlet. This cmdlet exports the database deployment resources to a .zip file, because the Path parameter ended in .zip.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$production = New-DatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production"
$build = Import-DatabaseBuildArtifact "C:\Work\buildArtifacts\DatabaseBuildArtifact.1.0.0.nupkg"
 
$release = New-DatabaseReleaseArtifact -Source $build -Target $production
$release | Export-DatabaseReleaseArtifact -Path "C:\Export\DatabaseRelease" -Format Zip</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to create database deployment resources and export them to a .zip file using the Format parameter.</maml:para>
          <maml:para>The Export-DatabaseReleaseArtifact cmdlet exports the database deployment resources to the .zip file, "C:\Export\DatabaseRelease.zip" because "Zip" is specified by the Format parameter. If the Format parameter wasn't used, the database deployment resources would be exported to a folder, because the Path parameter doesn't end in ".zip".</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Import-DatabaseReleaseArtifact -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Import-DatabaseReleaseArtifact</command:name>
      <command:verb>Import</command:verb>
      <command:noun>DatabaseReleaseArtifact</command:noun>
      <maml:description>
        <maml:para>Imports a Release Artifact, exported to disk by Export-DatabaseReleaseArtifact, from a folder or .zip file.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Import-DatabaseReleaseArtifact cmdlet re-imports the release artifact that has been exported to a folder or .zip file by the Export-DatabaseReleaseArtifact cmdlet.</maml:para>
      <maml:para>The IReleaseArtifact object produced can then be used by the Use-DatabaseReleaseArtifact cmdlet to deploy the update.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Import-DatabaseReleaseArtifact</maml:name>
        <!-- Parameter: Path -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="0">
          <maml:name>Path</maml:name>
          <maml:description>
            <maml:para>The path to the folder or .zip file you want to import.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: Path -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="0">
        <maml:name>Path</maml:name>
        <maml:description>
          <maml:para>The path to the folder or .zip file you want to import.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes />
    <command:returnValues>
      <!-- OutputType: IReleaseArtifact -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.ReleaseArtifacts.IReleaseArtifact</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$release = Import-DatabaseReleaseArtifact -Path "C:\Work\DatabaseRelease\"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to import a folder to create the database deployment resources.</maml:para>
          <maml:para>The Import-DatabaseReleaseArtifact cmdlet imports the folder C:\Work\DatabaseRelease\, creating the database deployment resources. This folder was created by exporting to C:\Work\DatabaseRelease\ using the Export-DatabaseReleaseArtifact cmdlet.</maml:para>
          <maml:para>Using Export-DatabaseReleaseArtifact and Import-DatabaseReleaseArtifact like this allows you to review the update script before you deploy with SQL Change Automation.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$release = Import-DatabaseReleaseArtifact -Path "C:\Work\DatabaseRelease.zip"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to import a .zip file to create the database deployment resources.</maml:para>
          <maml:para>The Import-DatabaseReleaseArtifact cmdlet imports the .zip file C:\Work\DatabaseRelease.zip, creating the database deployment resources.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: New-DatabaseReleaseArtifact -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>New-DatabaseReleaseArtifact</command:name>
      <command:verb>New</command:verb>
      <command:noun>DatabaseReleaseArtifact</command:noun>
      <maml:description>
        <maml:para>Generates a Release Artifact containing deployment resources for a specific environment.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The New-ReleaseArtifact cmdlet creates the database deployment resources containing all the information you need to update a target database. The output can be used by the Use-ReleaseArtifact cmdlet to update the target database, or by the Export-ReleaseArtifact cmdlet to export these resources for review.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: AbortOnWarningLevel -->
      <command:syntaxItem>
        <maml:name>New-DatabaseReleaseArtifact</maml:name>
        <!-- Parameter: Source -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Source</maml:name>
          <maml:description>
            <maml:para>The schema you want to update databases to. This can be:</maml:para>
            <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
            <maml:para>- a database connection string</maml:para>
            <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
            <maml:para>- a Database Build Artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
            <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
          </maml:description>
          <command:parameterValue required="true">object</command:parameterValue>
          <dev:type>
            <maml:name>System.Object</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Target -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Target</maml:name>
          <maml:description>
            <maml:para>A database schema you want to update from. This can be:</maml:para>
            <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
            <maml:para>- a database connection string</maml:para>
            <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
            <maml:para>- a Database Build Artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
            <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
            <maml:para>- a list containing one or more of the above</maml:para>
            <maml:para>If you use a list, the cmdlet will check that everything in the list has the same database schema. If there are no differences in schema, the cmdlet will create the Database Release. If there are any differences in schema, the cmdlet will fail and inform you.</maml:para>
          </maml:description>
          <command:parameterValue required="true">object</command:parameterValue>
          <dev:type>
            <maml:name>System.Object</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: AbortOnWarningLevel -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>AbortOnWarningLevel</maml:name>
          <maml:description>
            <maml:para>Use this parameter to set the minimum warning level that will cause the release generation operation to abort.</maml:para>
            <maml:para>Valid warning severity levels are:</maml:para>
            <maml:para>- High</maml:para>
            <maml:para>- Medium</maml:para>
            <maml:para>- Low</maml:para>
            <maml:para>- Information</maml:para>
            <maml:para>- None (do not abort for any warnings)</maml:para>
            <maml:para>The default setting is 'None'.</maml:para>
            <maml:para>Possible values: Information, Low, Medium, High, None</maml:para>
          </maml:description>
          <command:parameterValue required="true">WarningSeverity</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Shared.Domain.WarningSeverity</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>None</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Information</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Low</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Medium</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">High</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">None</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
        <!-- Parameter: CodeAnalysisSettingsPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>CodeAnalysisSettingsPath</maml:name>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: DriftFiltering -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>DriftFiltering</maml:name>
          <maml:description>
            <maml:para>Use this parameter to determine what objects should be included in the drift report.</maml:para>
            <maml:para>Valid options are:</maml:para>
            <maml:para>- 'ModifiedObjectsOnly': Include all objects which wouldn't be dropped in the drift correction script.</maml:para>
            <maml:para>- 'AllObjects': Include all objects, including those which would be dropped by the drift revert script.</maml:para>
            <maml:para>- 'ObjectsToBeUpdatedOnly': Only include those objects which will be updated in the current release. Dependencies are not handled.</maml:para>
            <maml:para>The default setting is 'ModifiedObjectsOnly'.</maml:para>
            <maml:para>This setting is applicable to SQL Change Automation projects only.</maml:para>
            <maml:para>Possible values: ModifiedObjectsOnly, AllObjects, ObjectsToBeUpdatedOnly</maml:para>
          </maml:description>
          <command:parameterValue required="true">DriftFiltering</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Commands.DriftFiltering</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>ModifiedObjectsOnly</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">ModifiedObjectsOnly</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">AllObjects</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ObjectsToBeUpdatedOnly</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Overrides any Filter.scpf file present in the Source schema with an alternative filter file to be used when generating the Update.sql change script and in all schema comparisons.</maml:para>
            <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
            <maml:para>For more information about filtering see https://www.red-gate.com/sca/ps/help/filters.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: IgnoreAdditional -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreAdditional</maml:name>
          <maml:description>
            <maml:para>Specifies whether to ignore additional objects in the target database. Enabling this prevents new and unexpected objects in the target being dropped - note that the checks and tests applied to this database may not have taken those objects into account and may therefore not be valid.</maml:para>
            <maml:para>This parameter can't be used simultaneously with filter files.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>Tells the SQL Compare engine to ignore parser errors.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IgnoreStaticData -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreStaticData</maml:name>
          <maml:description>
            <maml:para>If you use Red Gate SQL Source Control, you can flag tables that contain static data. If you specify a scripts folder or NuGet package as the value of Source and a database connection object or string as the value of Target, by default SQL Change Automation compares the data in these tables when generating the update script. Use this parameter to ignore static data when comparing the databases.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IncludeIdenticalsInReport -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IncludeIdenticalsInReport</maml:name>
          <maml:description>
            <maml:para>By default, the change report will show the number of identical objects, but won't show the full SQL for each object. Use this parameter to include the full SQL of identical objects.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: SqlCmdVariables -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SqlCmdVariables</maml:name>
          <command:parameterValue required="true">Hashtable</command:parameterValue>
          <dev:type>
            <maml:name>System.Collections.Hashtable</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when creating the update script and running pre- and post-deploy checks. SQL Change Automation applies a default set of options, listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreTSQLT</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TransactionIsolationLevel -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TransactionIsolationLevel</maml:name>
          <maml:description>
            <maml:para>The isolation level for the transactions used in the update script. Permitted values are Serializable, Snapshot, RepeatableRead, ReadCommitted and ReadUncommitted. The default level is Serializable.</maml:para>
            <maml:para>See https://docs.microsoft.com/sql/t-sql/statements/set-transaction-isolation-level-transact-sql for more details on transaction isolation levels.</maml:para>
            <maml:para>Possible values: Serializable, Snapshot, RepeatableRead, ReadCommitted, ReadUncommitted</maml:para>
          </maml:description>
          <command:parameterValue required="true">TransactionIsolationLevel</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Shared.Domain.TransactionIsolationLevel</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>Serializable</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Serializable</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Snapshot</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">RepeatableRead</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadCommitted</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadUncommitted</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: Source -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>Source</maml:name>
        <maml:description>
          <maml:para>The schema you want to update databases to. This can be:</maml:para>
          <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
          <maml:para>- a database connection string</maml:para>
          <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
          <maml:para>- a Database Build Artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
          <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
        </maml:description>
        <command:parameterValue required="true">object</command:parameterValue>
        <dev:type>
          <maml:name>System.Object</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Target -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>Target</maml:name>
        <maml:description>
          <maml:para>A database schema you want to update from. This can be:</maml:para>
          <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
          <maml:para>- a database connection string</maml:para>
          <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
          <maml:para>- a Database Build Artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
          <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
          <maml:para>- a list containing one or more of the above</maml:para>
          <maml:para>If you use a list, the cmdlet will check that everything in the list has the same database schema. If there are no differences in schema, the cmdlet will create the Database Release. If there are any differences in schema, the cmdlet will fail and inform you.</maml:para>
        </maml:description>
        <command:parameterValue required="true">object</command:parameterValue>
        <dev:type>
          <maml:name>System.Object</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: FilterPath -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>FilterPath</maml:name>
        <maml:description>
          <maml:para>The path to a .scpf filter file.</maml:para>
          <maml:para>Overrides any Filter.scpf file present in the Source schema with an alternative filter file to be used when generating the Update.sql change script and in all schema comparisons.</maml:para>
          <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
          <maml:para>For more information about filtering see https://www.red-gate.com/sca/ps/help/filters.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: IgnoreStaticData -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreStaticData</maml:name>
        <maml:description>
          <maml:para>If you use Red Gate SQL Source Control, you can flag tables that contain static data. If you specify a scripts folder or NuGet package as the value of Source and a database connection object or string as the value of Target, by default SQL Change Automation compares the data in these tables when generating the update script. Use this parameter to ignore static data when comparing the databases.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: SQLCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Compare options to use when creating the update script and running pre- and post-deploy checks. SQL Change Automation applies a default set of options, listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
          <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
          <maml:para>By default, the following Compare options are used:</maml:para>
          <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
          <maml:para>- DecryptEncryptedObjects</maml:para>
          <maml:para>- DoNotOutputCommentHeader</maml:para>
          <maml:para>- ForceColumnOrder</maml:para>
          <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
          <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
          <maml:para>- IgnoreTSQLT</maml:para>
          <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
          <maml:para>- IgnoreUserProperties</maml:para>
          <maml:para>- IgnoreWhiteSpace</maml:para>
          <maml:para>- IgnoreWithElementOrder</maml:para>
          <maml:para>- IncludeDependencies</maml:para>
          <maml:para>- ThrowOnFileParseFailed</maml:para>
          <maml:para>- UseCompatibilityLevel</maml:para>
          <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: SQLDataCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLDataCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: IgnoreAdditional -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreAdditional</maml:name>
        <maml:description>
          <maml:para>Specifies whether to ignore additional objects in the target database. Enabling this prevents new and unexpected objects in the target being dropped - note that the checks and tests applied to this database may not have taken those objects into account and may therefore not be valid.</maml:para>
          <maml:para>This parameter can't be used simultaneously with filter files.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: TransactionIsolationLevel -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TransactionIsolationLevel</maml:name>
        <maml:description>
          <maml:para>The isolation level for the transactions used in the update script. Permitted values are Serializable, Snapshot, RepeatableRead, ReadCommitted and ReadUncommitted. The default level is Serializable.</maml:para>
          <maml:para>See https://docs.microsoft.com/sql/t-sql/statements/set-transaction-isolation-level-transact-sql for more details on transaction isolation levels.</maml:para>
          <maml:para>Possible values: Serializable, Snapshot, RepeatableRead, ReadCommitted, ReadUncommitted</maml:para>
        </maml:description>
        <command:parameterValue required="true">TransactionIsolationLevel</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Shared.Domain.TransactionIsolationLevel</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>Serializable</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Serializable</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Snapshot</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">RepeatableRead</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">ReadCommitted</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">ReadUncommitted</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
      <!-- Parameter: IncludeIdenticalsInReport -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IncludeIdenticalsInReport</maml:name>
        <maml:description>
          <maml:para>By default, the change report will show the number of identical objects, but won't show the full SQL for each object. Use this parameter to include the full SQL of identical objects.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: AbortOnWarningLevel -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>AbortOnWarningLevel</maml:name>
        <maml:description>
          <maml:para>Use this parameter to set the minimum warning level that will cause the release generation operation to abort.</maml:para>
          <maml:para>Valid warning severity levels are:</maml:para>
          <maml:para>- High</maml:para>
          <maml:para>- Medium</maml:para>
          <maml:para>- Low</maml:para>
          <maml:para>- Information</maml:para>
          <maml:para>- None (do not abort for any warnings)</maml:para>
          <maml:para>The default setting is 'None'.</maml:para>
          <maml:para>Possible values: Information, Low, Medium, High, None</maml:para>
        </maml:description>
        <command:parameterValue required="true">WarningSeverity</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Shared.Domain.WarningSeverity</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>None</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Information</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Low</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Medium</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">High</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">None</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
      <!-- Parameter: IgnoreParserErrors -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreParserErrors</maml:name>
        <maml:description>
          <maml:para>Tells the SQL Compare engine to ignore parser errors.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: SqlCmdVariables -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SqlCmdVariables</maml:name>
        <command:parameterValue required="true">Hashtable</command:parameterValue>
        <dev:type>
          <maml:name>System.Collections.Hashtable</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: CodeAnalysisSettingsPath -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>CodeAnalysisSettingsPath</maml:name>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: DriftFiltering -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>DriftFiltering</maml:name>
        <maml:description>
          <maml:para>Use this parameter to determine what objects should be included in the drift report.</maml:para>
          <maml:para>Valid options are:</maml:para>
          <maml:para>- 'ModifiedObjectsOnly': Include all objects which wouldn't be dropped in the drift correction script.</maml:para>
          <maml:para>- 'AllObjects': Include all objects, including those which would be dropped by the drift revert script.</maml:para>
          <maml:para>- 'ObjectsToBeUpdatedOnly': Only include those objects which will be updated in the current release. Dependencies are not handled.</maml:para>
          <maml:para>The default setting is 'ModifiedObjectsOnly'.</maml:para>
          <maml:para>This setting is applicable to SQL Change Automation projects only.</maml:para>
          <maml:para>Possible values: ModifiedObjectsOnly, AllObjects, ObjectsToBeUpdatedOnly</maml:para>
        </maml:description>
        <command:parameterValue required="true">DriftFiltering</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Commands.DriftFiltering</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>ModifiedObjectsOnly</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">ModifiedObjectsOnly</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">AllObjects</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">ObjectsToBeUpdatedOnly</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
    </command:parameters>
    <command:inputTypes />
    <command:returnValues>
      <!-- OutputType: IReleaseArtifact -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.ReleaseArtifacts.IReleaseArtifact</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2017" -Database "Staging"
New-DatabaseReleaseArtifact -Source "C:\Work\buildArtifacts\DatabaseBuildArtifact.1.0.0.nupkg" -Target $staging</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use a SQL Change Automation Build Artifact as a source.</maml:para>
          <maml:para>The New-DatabaseReleaseArtifact cmdlet uses a SQL Change Automation Build Artifact, DatabaseBuildArtifact.1.0.0.nupkg, as the Source parameter. The package must have been generated from a SQL Change Automation project using the New-DatabaseBuildArtifact cmdlet</maml:para>
          <maml:para>The Target parameter must be a connection string or a DatabaseConnection when using SQL Change Automation Projects.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging"
$buildArtifact = "C:\Work\buildArtifacts\MyDatabase.1.0.0.nupkg"
 
New-DatabaseReleaseArtifact -Source $buildArtifact -Target $staging</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use a SQL Source Control Build Artifact to specify the source schema.</maml:para>
          <maml:para>The New-DatabaseReleaseArtifact cmdlet uses a NuGet database package, MyDatabase.1.0.0.nupkg, as the Source parameter. The package must contain a scripts folder in the db\state sub-folder.</maml:para>
          <maml:para>If the NuGet package includes tables that have been flagged as containing static data, this data will be included when generating the Release Artifact, unless the IgnoreStaticData parameter is specified.</maml:para>
          <maml:para>You can also specify a NuGet package as the Target parameter. However, if you do this, static data won't be deployed.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging"
$test = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test" -Username "AutomationUser" -Password "P@ssw0rd"
 
New-DatabaseReleaseArtifact -Source $test -Target $staging</dev:code>
        <dev:remarks>
          <maml:para>This example show how to create the database deployment resources using two database connections.</maml:para>
          <maml:para>The New-DatabaseConnection cmdlet creates two Database Connection objects, $staging and $test. $staging is used to connect to the Staging database on staging01\sql2014. $test is used to connect to the Test database on test01\sql2014.</maml:para>
          <maml:para>The New-DatabaseReleaseArtifact cmdlet uses $test as the Source parameter, and $staging as the Target parameter. The cmdlet creates the database deployment resources that can be used to update the schema of Staging (and any database with the same schema as Staging) to match the schema of Test.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 4 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging"
$test = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test"
 
$options = "IgnoreComments, AddObjectExistenceChecks, -ForceColumnOrder"
 
New-DatabaseReleaseArtifact -Source $test -Target $staging -SQLCompareOptions $options</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify the SQL Compare options that are used when generating the update script and running pre- and post-deploy checks.</maml:para>
          <maml:para>In this example, the $options variable specifies that IgnoreComments and AddObjectExistenceChecks should be included in addition to the default set of SQL Compare options. The minus sign before ForceColumnOrder indicates that this default option will be turned off.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 5 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging"
$test = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test"
 
$filter = "C:\Work\MyFilter.scpf"
 
New-DatabaseReleaseArtifact -Source $test -Target $staging -FilterPath $filter</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use a specific filter file to include/exclude database objects when generating the update script, overriding any filter file present in the source schema.</maml:para>
          <maml:para>MyFilter.scpf defines which database objects are considered when the update script is generated. If this update is used, the filters will also be used in pre- and post-schema comparisons.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 6 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2017" -Database "Staging"
$sqlCmdVariables = @{MyVar = 'SomeVar'; MyOtherVar = '1234'}
New-DatabaseReleaseArtifact -Source "C:\Work\buildArtifacts\DatabaseBuildArtifact.1.0.0.nupkg" -Target $staging -SqlCmdVariables $sqlCmdVariables</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use a SQL Change Automation Build Artifact as a source with custom SQLCMD variables specified in the form of a hashtable.</maml:para>
          <maml:para>Any necessary escaping will be performed, so take care not to double escape</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 7 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2017" -Database "Staging"
$releaseArtifact = New-DatabaseReleaseArtifact -Source "C:\Work\buildArtifacts\DatabaseBuildArtifact.1.0.0.nupkg" -Target $staging
$releaseArtifact | Export-DatabaseReleaseArtifact -Path "C:\MyRelease" -Format Folder
$driftStatus = $releaseArtifact.DriftStatus | Out-String
if ($releaseArtifact.DriftStatus -eq 'Drifted')
{
  Write-Error "Drift detected. Please see drift report in exported release artifact for more information."
}</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to fail a build if drift is detected on the target database.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Use-DatabaseReleaseArtifact -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Use-DatabaseReleaseArtifact</command:name>
      <command:verb>Use</command:verb>
      <command:noun>DatabaseReleaseArtifact</command:noun>
      <maml:description>
        <maml:para>Uses the IReleaseArtifact object produced by the New-DatabaseReleaseArtifact cmdlet to update a target database.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Use-DatabaseReleaseArtifact cmdlet executes the SQL update script inside the database deployment resources produced by the New-DatabaseReleaseArtifact cmdlet. This updates the target database to the same state as the schema specified in the IReleaseArtifact object.</maml:para>
      <maml:para>Before executing the script, SQL Change Automation first checks that the target database schema matches the target schema defined in the IReleaseArtifact object. If the schemas don't match, SQL Change Automation will then check if the target database schema matches the source schema specified in the Use-DatabaseReleaseArtifact cmdlet. (This is to check if the update has already been applied and the target schema is already in the desired state). If these schemas also don't match, the cmdlet fails. If the checks show the target schema is already in the desired state, SQL Change Automation will skip running the SQL update script and the cmdlet will finish. To turn off these checks, use the SkipPreUpdateSchemaCheck parameter.</maml:para>
      <maml:para>The Use-DatabaseReleaseArtifact cmdlet then executes the SQL script to update the target database. It logs any errors that occur in the execution, but will continue executing the whole script unless the connection to the database is broken (for example, if the database goes offline).</maml:para>
      <maml:para>After executing the script, the cmdlet checks that the target database schema has updated correctly to the 'Source' schema specified in the New-DatabaseReleaseArtifact cmdlet. If the schema hasn't updated correctly, the cmdlet returns an error message. To turn off this check use the SkipPostUpdateSchemaCheck parameter.</maml:para>
      <maml:para>By default, SQL Change Automation deploys static data contained in a NuGet package, scripts folder or zip file; no data will be deployed from a live data source. The pre-update and post-update schema checks also check for differences in static data. To turn off the deployment of static data and to exclude static data from the schema checks, add IgnoreStaticData to the New-DatabaseReleaseArtifact command. For more information about static data, see http://www.red-gate.com/sca/ps/help/staticdata.</maml:para>
      <maml:para>If the database deployment resources contain a filter, this will be applied to the pre-deployment and post-deployment schema checks; only differences between objects included by the filter will cause the check to fail. For more information about filters, see http://www.red-gate.com/sca/ps/help/filters.</maml:para>
      <maml:para>The SQL Compare options specified in the IReleaseArtifact object will be used in the schema comparison checks before and after running the update. For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: AbortOnWarningLevel -->
      <command:syntaxItem>
        <maml:name>Use-DatabaseReleaseArtifact</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The Release Artifact to be deployed.</maml:para>
          </maml:description>
          <command:parameterValue required="true">IReleaseArtifact</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.Domain.ReleaseArtifacts.IReleaseArtifact</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: DeployTo -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>DeployTo</maml:name>
          <maml:description>
            <maml:para>A Database Connection object or database connection string that identifies the target database to be updated. See New-DatabaseConnection for details.</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: AbortOnWarningLevel -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>AbortOnWarningLevel</maml:name>
          <maml:description>
            <maml:para>Use this parameter to set the minimum warning level that will cause the release execution operation to abort.</maml:para>
            <maml:para>Valid warning severity levels are:</maml:para>
            <maml:para>- High</maml:para>
            <maml:para>- Medium</maml:para>
            <maml:para>- Low</maml:para>
            <maml:para>- Information</maml:para>
            <maml:para>- None (do not abort for any warnings)</maml:para>
            <maml:para>The default setting is 'None'.</maml:para>
            <maml:para>Possible values: Information, Low, Medium, High, None</maml:para>
          </maml:description>
          <command:parameterValue required="true">WarningSeverity</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Shared.Domain.WarningSeverity</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>None</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Information</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Low</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Medium</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">High</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">None</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
        <!-- Parameter: DisableMonitorAnnotation -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>DisableMonitorAnnotation</maml:name>
          <maml:description>
            <maml:para>Don't add annotations to the event log for SQL Monitor.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: DriftHandling -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>DriftHandling</maml:name>
          <maml:description>
            <maml:para>Use this parameter to revert drift.</maml:para>
            <maml:para>Valid options are:</maml:para>
            <maml:para>- 'Ignore': No drift handling will be performed. The migrations scripts will be executed against the target database as normal.</maml:para>
            <maml:para>- 'RevertOnly': The drift revert script will be executed against the target database. No migrations will be deployed.</maml:para>
            <maml:para>- 'RevertAndDeploy': The drift revert script will be executed against the target database and then the migrations will be deployed.</maml:para>
            <maml:para>The default setting is 'Ignore'.</maml:para>
            <maml:para>This setting is applicable to SQL Change Automation projects only.</maml:para>
            <maml:para>Possible values: Ignore, RevertOnly, RevertAndDeploy</maml:para>
          </maml:description>
          <command:parameterValue required="true">DriftHandling</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.DeployRelease.DriftHandling</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>Ignore</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Ignore</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">RevertOnly</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">RevertAndDeploy</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
        <!-- Parameter: QueryBatchTimeout -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>QueryBatchTimeout</maml:name>
          <maml:description>
            <maml:para>The execution timeout, in seconds, for each batch of queries in the update script. The default value is 30 seconds. A value of zero indicates that no execution timeout will be enforced.</maml:para>
          </maml:description>
          <command:parameterValue required="true">int</command:parameterValue>
          <dev:type>
            <maml:name>System.Int32</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>30</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: ReleaseUrl -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>ReleaseUrl</maml:name>
          <maml:description>
            <maml:para>A web page to link this release to. Will be included in the SQL Monitor annotation.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SkipPostUpdateSchemaCheck -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SkipPostUpdateSchemaCheck</maml:name>
          <maml:description>
            <maml:para>Don't check that the target database has the correct schema after the update has run.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: SkipPreUpdateSchemaCheck -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SkipPreUpdateSchemaCheck</maml:name>
          <maml:description>
            <maml:para>Before running the update script, don't check that the target database has the correct schema or that the target database has already been updated.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The Release Artifact to be deployed.</maml:para>
        </maml:description>
        <command:parameterValue required="true">IReleaseArtifact</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.ReleaseArtifacts.IReleaseArtifact</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: DeployTo -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>DeployTo</maml:name>
        <maml:description>
          <maml:para>A Database Connection object or database connection string that identifies the target database to be updated. See New-DatabaseConnection for details.</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: SkipPreUpdateSchemaCheck -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SkipPreUpdateSchemaCheck</maml:name>
        <maml:description>
          <maml:para>Before running the update script, don't check that the target database has the correct schema or that the target database has already been updated.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: SkipPostUpdateSchemaCheck -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SkipPostUpdateSchemaCheck</maml:name>
        <maml:description>
          <maml:para>Don't check that the target database has the correct schema after the update has run.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: QueryBatchTimeout -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>QueryBatchTimeout</maml:name>
        <maml:description>
          <maml:para>The execution timeout, in seconds, for each batch of queries in the update script. The default value is 30 seconds. A value of zero indicates that no execution timeout will be enforced.</maml:para>
        </maml:description>
        <command:parameterValue required="true">int</command:parameterValue>
        <dev:type>
          <maml:name>System.Int32</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>30</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: AbortOnWarningLevel -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>AbortOnWarningLevel</maml:name>
        <maml:description>
          <maml:para>Use this parameter to set the minimum warning level that will cause the release execution operation to abort.</maml:para>
          <maml:para>Valid warning severity levels are:</maml:para>
          <maml:para>- High</maml:para>
          <maml:para>- Medium</maml:para>
          <maml:para>- Low</maml:para>
          <maml:para>- Information</maml:para>
          <maml:para>- None (do not abort for any warnings)</maml:para>
          <maml:para>The default setting is 'None'.</maml:para>
          <maml:para>Possible values: Information, Low, Medium, High, None</maml:para>
        </maml:description>
        <command:parameterValue required="true">WarningSeverity</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Shared.Domain.WarningSeverity</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>None</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Information</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Low</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Medium</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">High</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">None</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
      <!-- Parameter: DisableMonitorAnnotation -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>DisableMonitorAnnotation</maml:name>
        <maml:description>
          <maml:para>Don't add annotations to the event log for SQL Monitor.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: ReleaseUrl -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>ReleaseUrl</maml:name>
        <maml:description>
          <maml:para>A web page to link this release to. Will be included in the SQL Monitor annotation.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: DriftHandling -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>DriftHandling</maml:name>
        <maml:description>
          <maml:para>Use this parameter to revert drift.</maml:para>
          <maml:para>Valid options are:</maml:para>
          <maml:para>- 'Ignore': No drift handling will be performed. The migrations scripts will be executed against the target database as normal.</maml:para>
          <maml:para>- 'RevertOnly': The drift revert script will be executed against the target database. No migrations will be deployed.</maml:para>
          <maml:para>- 'RevertAndDeploy': The drift revert script will be executed against the target database and then the migrations will be deployed.</maml:para>
          <maml:para>The default setting is 'Ignore'.</maml:para>
          <maml:para>This setting is applicable to SQL Change Automation projects only.</maml:para>
          <maml:para>Possible values: Ignore, RevertOnly, RevertAndDeploy</maml:para>
        </maml:description>
        <command:parameterValue required="true">DriftHandling</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.DeployRelease.DriftHandling</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>Ignore</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Ignore</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">RevertOnly</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">RevertAndDeploy</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.ReleaseArtifacts.IReleaseArtifact</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The Release Artifact to be deployed.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: None -->
      <command:returnValue>
        <dev:type>
          <maml:name>None</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$production = New-DatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production" -Username "AutomationUser" -Password "P@ssw0rd"
$build = Import-DatabaseBuildArtifact "C:\Work\buildArtifacts\DatabaseBuildArtifact.1.0.0.nupkg"
 
$update = New-DatabaseReleaseArtifact -Source $build -Target $production
 
Use-DatabaseReleaseArtifact $update -DeployTo $production</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to update a database based on a SQL Change Automation Build Artifact, DatabaseBuildArtifact.1.0.0.nupkg.</maml:para>
          <maml:para>This cmdlet runs the targeted deployment script contained in the IReleaseArtifact, which updates the database "Production".</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging" -Username "AutomationUser" -Password "P@ssw0rd"
$buildArtifact = "C:\Work\buildArtifacts\MyDatabase.1.0.0.nupkg"
 
$update = New-DatabaseReleaseArtifact -Source $buildArtifact -Target $staging
 
Use-DatabaseReleaseArtifact $update -DeployTo $staging</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to update a database based on a SQL Source Control Build Artifact, MyDatabase.1.0.0.nupkg.</maml:para>
          <maml:para>The New-DatabaseReleaseArtifact cmdlet creates the database deployment resources. It uses the database, Staging, as the Target parameter: this is the schema to be updated. It uses a NuGet package containing a scripts folder, database.nupkg, as the Source parameter: this is the schema that Staging will be updated to.</maml:para>
          <maml:para>The IReleaseArtifact object, $update, is then passed to the Use-DatabaseReleaseArtifact cmdlet. This cmdlet runs the SQL update script contained in $update, which updates Staging to the schema contained in database.nupkg.</maml:para>
          <maml:para>Before running the SQL update script, Use-DatabaseReleaseArtifact checks that Staging still has the same schema that it did at the time that $update was created. It then runs the script, and afterwards, checks that the update was successful and that Staging has the correct new schema.</maml:para>
          <maml:para>If $package contains static data, SQL Change Automation will deploy it to the $staging database. The pre-deployment and post-deployment schema checks also check for differences in static data. To turn off the deployment of static data and to exclude static data from the schema checks, add the IgnoreStaticData parameter to New-DatabaseReleaseArtifact.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging" -Username "AutomationUser" -Password "P@ssw0rd"
$buildArtifact = "C:\Work\buildArtifacts\MyDatabase.1.0.0.nupkg"
 
$update = New-DatabaseReleaseArtifact -Source $buildArtifact -Target $staging
 
Use-DatabaseReleaseArtifact $update -DeployTo $staging -SkipPostUpdateSchemaCheck</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to skip the post-deployment check that verifies the target database matches the source.</maml:para>
          <maml:para>The Use-DatabaseReleaseArtifact cmdlet updates the database, Staging, to match the schema contained in the NuGet package, database.nupkg. The SkipPostUpdateSchemaCheck parameter is used to skip the post-update schema check.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 4 ----------</maml:title>
        <dev:code>$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging" -Username "AutomationUser" -Password "P@ssw0rd"
 
Import-DatabaseReleaseArtifact -Path "C:\Work\DatabaseRelease" | Use-DatabaseReleaseArtifact -DeployTo $staging</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Import-DatabaseReleaseArtifact cmdlet to import the database deployment resources from a folder created previously by the Export-DatabaseReleaseArtifact cmdlet. The database, Staging, is updated to the schema specified by the IReleaseArtifact object.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Sync-DatabaseSchema -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Sync-DatabaseSchema</command:name>
      <command:verb>Sync</command:verb>
      <command:noun>DatabaseSchema</command:noun>
      <maml:description>
        <maml:para>Updates a target database schema to match a source database schema.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Sync-DatabaseSchema cmdlet updates a target database to match a source database schema.</maml:para>
      <maml:para>The source schema can be a database connection, a build artifact, or a SQL Source Control project. The target schema must be a database connection.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: AbortOnWarningLevel -->
      <command:syntaxItem>
        <maml:name>Sync-DatabaseSchema</maml:name>
        <!-- Parameter: Source -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Source</maml:name>
          <maml:description>
            <maml:para>The source database schema used to update the target database. This can be:</maml:para>
            <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
            <maml:para>- a database connection string</maml:para>
            <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
            <maml:para>- a Database Build Artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
            <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
          </maml:description>
          <command:parameterValue required="true">object</command:parameterValue>
          <dev:type>
            <maml:name>System.Object</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Target -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Target</maml:name>
          <maml:description>
            <maml:para>The target database to be updated. This can be:</maml:para>
            <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
            <maml:para>- a database connection string</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: AbortOnWarningLevel -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>AbortOnWarningLevel</maml:name>
          <maml:description>
            <maml:para>Use this parameter to set the minimum warning level that will cause the sync operation to abort.</maml:para>
            <maml:para>Valid warning severity levels are:</maml:para>
            <maml:para>- High</maml:para>
            <maml:para>- Medium</maml:para>
            <maml:para>- Low</maml:para>
            <maml:para>- Information</maml:para>
            <maml:para>- None (do not abort for any warnings)</maml:para>
            <maml:para>The default setting is 'High'.</maml:para>
            <maml:para>This parameter can't be used in addition to the Force parameter.</maml:para>
            <maml:para>Possible values: Information, Low, Medium, High, None</maml:para>
          </maml:description>
          <command:parameterValue required="true">WarningSeverity</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Shared.Domain.WarningSeverity</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>High</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Information</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Low</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Medium</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">High</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">None</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Use this parameter to specify a filter file to be used when performing the sync operation. This will override any Filter.scpf file in the source.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: IgnoreAdditional -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreAdditional</maml:name>
          <maml:description>
            <maml:para>When SQL Change Automation performs a sync operation, by default it will drop all additional objects in the target database.</maml:para>
            <maml:para>If you specify this parameter, additional objects will be ignored.</maml:para>
            <maml:para>Enabling this prevents new and unexpected objects in the target being dropped - note that the checks and tests applied to this database may not have taken those objects into account and may therefore not be valid.</maml:para>
            <maml:para>This parameter can't be used simultaneously with filter files.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>Use this parameter to force the SQL Compare engine to ignore any parser errors.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IgnoreStaticData -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreStaticData</maml:name>
          <maml:description>
            <maml:para>When SQL Change Automation performs a sync operation and the source is a NuGet package or a SQL Source Control project, by default it will include static data flagged by SQL Source Control.</maml:para>
            <maml:para>If you specify this parameter, static data will be ignored.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: QueryBatchTimeout -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>QueryBatchTimeout</maml:name>
          <maml:description>
            <maml:para>The execution timeout, in seconds, for each batch of queries during the sync operation. The default value is 30 seconds. A value of zero indicates that no execution timeout will be enforced.</maml:para>
          </maml:description>
          <command:parameterValue required="true">int</command:parameterValue>
          <dev:type>
            <maml:name>System.Int32</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>0</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: SqlCmdVariables -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SqlCmdVariables</maml:name>
          <command:parameterValue required="true">Hashtable</command:parameterValue>
          <dev:type>
            <maml:name>System.Collections.Hashtable</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when performing the sync operation. SQL Change Automation applies a default set of options (listed below). To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreTSQLT</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TransactionIsolationLevel -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TransactionIsolationLevel</maml:name>
          <maml:description>
            <maml:para>Use this parameter to specify the isolation level for the transactions during the sync operation. Permitted values are: Serializable, Snapshot, RepeatableRead, ReadCommitted and ReadUncommitted. The default level is Serializable.</maml:para>
            <maml:para>See https://docs.microsoft.com/sql/t-sql/statements/set-transaction-isolation-level-transact-sql for more details on transaction isolation levels.</maml:para>
            <maml:para>Possible values: Serializable, Snapshot, RepeatableRead, ReadCommitted, ReadUncommitted</maml:para>
          </maml:description>
          <command:parameterValue required="true">TransactionIsolationLevel</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Shared.Domain.TransactionIsolationLevel</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>Serializable</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Serializable</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Snapshot</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">RepeatableRead</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadCommitted</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadUncommitted</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
      </command:syntaxItem>
      <!-- Parameter set: Force -->
      <command:syntaxItem>
        <maml:name>Sync-DatabaseSchema</maml:name>
        <!-- Parameter: Source -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Source</maml:name>
          <maml:description>
            <maml:para>The source database schema used to update the target database. This can be:</maml:para>
            <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
            <maml:para>- a database connection string</maml:para>
            <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
            <maml:para>- a Database Build Artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
            <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
          </maml:description>
          <command:parameterValue required="true">object</command:parameterValue>
          <dev:type>
            <maml:name>System.Object</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Target -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>Target</maml:name>
          <maml:description>
            <maml:para>The target database to be updated. This can be:</maml:para>
            <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
            <maml:para>- a database connection string</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Use this parameter to specify a filter file to be used when performing the sync operation. This will override any Filter.scpf file in the source.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Force -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Force</maml:name>
          <maml:description>
            <maml:para>Use this parameter to prevent the sync operation from aborting regardless of any warnings.</maml:para>
            <maml:para>An alternative way of doing this is to set the AbortOnWarningLevel to 'None'.</maml:para>
            <maml:para>This parameter can't be used in addition to the AbortOnWarningLevel parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IgnoreAdditional -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreAdditional</maml:name>
          <maml:description>
            <maml:para>When SQL Change Automation performs a sync operation, by default it will drop all additional objects in the target database.</maml:para>
            <maml:para>If you specify this parameter, additional objects will be ignored.</maml:para>
            <maml:para>Enabling this prevents new and unexpected objects in the target being dropped - note that the checks and tests applied to this database may not have taken those objects into account and may therefore not be valid.</maml:para>
            <maml:para>This parameter can't be used simultaneously with filter files.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>Use this parameter to force the SQL Compare engine to ignore any parser errors.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IgnoreStaticData -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreStaticData</maml:name>
          <maml:description>
            <maml:para>When SQL Change Automation performs a sync operation and the source is a NuGet package or a SQL Source Control project, by default it will include static data flagged by SQL Source Control.</maml:para>
            <maml:para>If you specify this parameter, static data will be ignored.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: QueryBatchTimeout -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>QueryBatchTimeout</maml:name>
          <maml:description>
            <maml:para>The execution timeout, in seconds, for each batch of queries during the sync operation. The default value is 30 seconds. A value of zero indicates that no execution timeout will be enforced.</maml:para>
          </maml:description>
          <command:parameterValue required="true">int</command:parameterValue>
          <dev:type>
            <maml:name>System.Int32</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>0</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: SqlCmdVariables -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SqlCmdVariables</maml:name>
          <command:parameterValue required="true">Hashtable</command:parameterValue>
          <dev:type>
            <maml:name>System.Collections.Hashtable</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when performing the sync operation. SQL Change Automation applies a default set of options (listed below). To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreTSQLT</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TransactionIsolationLevel -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TransactionIsolationLevel</maml:name>
          <maml:description>
            <maml:para>Use this parameter to specify the isolation level for the transactions during the sync operation. Permitted values are: Serializable, Snapshot, RepeatableRead, ReadCommitted and ReadUncommitted. The default level is Serializable.</maml:para>
            <maml:para>See https://docs.microsoft.com/sql/t-sql/statements/set-transaction-isolation-level-transact-sql for more details on transaction isolation levels.</maml:para>
            <maml:para>Possible values: Serializable, Snapshot, RepeatableRead, ReadCommitted, ReadUncommitted</maml:para>
          </maml:description>
          <command:parameterValue required="true">TransactionIsolationLevel</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Shared.Domain.TransactionIsolationLevel</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>Serializable</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Serializable</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">Snapshot</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">RepeatableRead</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadCommitted</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">ReadUncommitted</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: Source -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>Source</maml:name>
        <maml:description>
          <maml:para>The source database schema used to update the target database. This can be:</maml:para>
          <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
          <maml:para>- a database connection string</maml:para>
          <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
          <maml:para>- a Database Build Artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
          <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
        </maml:description>
        <command:parameterValue required="true">object</command:parameterValue>
        <dev:type>
          <maml:name>System.Object</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Target -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>Target</maml:name>
        <maml:description>
          <maml:para>The target database to be updated. This can be:</maml:para>
          <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
          <maml:para>- a database connection string</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: FilterPath -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>FilterPath</maml:name>
        <maml:description>
          <maml:para>The path to a .scpf filter file.</maml:para>
          <maml:para>Use this parameter to specify a filter file to be used when performing the sync operation. This will override any Filter.scpf file in the source.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: IgnoreStaticData -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreStaticData</maml:name>
        <maml:description>
          <maml:para>When SQL Change Automation performs a sync operation and the source is a NuGet package or a SQL Source Control project, by default it will include static data flagged by SQL Source Control.</maml:para>
          <maml:para>If you specify this parameter, static data will be ignored.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: IgnoreAdditional -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreAdditional</maml:name>
        <maml:description>
          <maml:para>When SQL Change Automation performs a sync operation, by default it will drop all additional objects in the target database.</maml:para>
          <maml:para>If you specify this parameter, additional objects will be ignored.</maml:para>
          <maml:para>Enabling this prevents new and unexpected objects in the target being dropped - note that the checks and tests applied to this database may not have taken those objects into account and may therefore not be valid.</maml:para>
          <maml:para>This parameter can't be used simultaneously with filter files.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: SQLCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Compare options to use when performing the sync operation. SQL Change Automation applies a default set of options (listed below). To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
          <maml:para>This parameter will be ignored if the value specified is $null or empty.</maml:para>
          <maml:para>By default, the following Compare options are used:</maml:para>
          <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
          <maml:para>- DecryptEncryptedObjects</maml:para>
          <maml:para>- DoNotOutputCommentHeader</maml:para>
          <maml:para>- ForceColumnOrder</maml:para>
          <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
          <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
          <maml:para>- IgnoreTSQLT</maml:para>
          <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
          <maml:para>- IgnoreUserProperties</maml:para>
          <maml:para>- IgnoreWhiteSpace</maml:para>
          <maml:para>- IgnoreWithElementOrder</maml:para>
          <maml:para>- IncludeDependencies</maml:para>
          <maml:para>- ThrowOnFileParseFailed</maml:para>
          <maml:para>- UseCompatibilityLevel</maml:para>
          <maml:para>For more information about SQL Compare options, see http://www.red-gate.com/sca/ps/help/compareoptions.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: SQLDataCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLDataCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TransactionIsolationLevel -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TransactionIsolationLevel</maml:name>
        <maml:description>
          <maml:para>Use this parameter to specify the isolation level for the transactions during the sync operation. Permitted values are: Serializable, Snapshot, RepeatableRead, ReadCommitted and ReadUncommitted. The default level is Serializable.</maml:para>
          <maml:para>See https://docs.microsoft.com/sql/t-sql/statements/set-transaction-isolation-level-transact-sql for more details on transaction isolation levels.</maml:para>
          <maml:para>Possible values: Serializable, Snapshot, RepeatableRead, ReadCommitted, ReadUncommitted</maml:para>
        </maml:description>
        <command:parameterValue required="true">TransactionIsolationLevel</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Shared.Domain.TransactionIsolationLevel</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>Serializable</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Serializable</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Snapshot</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">RepeatableRead</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">ReadCommitted</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">ReadUncommitted</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
      <!-- Parameter: QueryBatchTimeout -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>QueryBatchTimeout</maml:name>
        <maml:description>
          <maml:para>The execution timeout, in seconds, for each batch of queries during the sync operation. The default value is 30 seconds. A value of zero indicates that no execution timeout will be enforced.</maml:para>
        </maml:description>
        <command:parameterValue required="true">int</command:parameterValue>
        <dev:type>
          <maml:name>System.Int32</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>0</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: AbortOnWarningLevel -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>AbortOnWarningLevel</maml:name>
        <maml:description>
          <maml:para>Use this parameter to set the minimum warning level that will cause the sync operation to abort.</maml:para>
          <maml:para>Valid warning severity levels are:</maml:para>
          <maml:para>- High</maml:para>
          <maml:para>- Medium</maml:para>
          <maml:para>- Low</maml:para>
          <maml:para>- Information</maml:para>
          <maml:para>- None (do not abort for any warnings)</maml:para>
          <maml:para>The default setting is 'High'.</maml:para>
          <maml:para>This parameter can't be used in addition to the Force parameter.</maml:para>
          <maml:para>Possible values: Information, Low, Medium, High, None</maml:para>
        </maml:description>
        <command:parameterValue required="true">WarningSeverity</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Shared.Domain.WarningSeverity</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>High</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Information</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Low</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">Medium</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">High</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">None</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
      <!-- Parameter: Force -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Force</maml:name>
        <maml:description>
          <maml:para>Use this parameter to prevent the sync operation from aborting regardless of any warnings.</maml:para>
          <maml:para>An alternative way of doing this is to set the AbortOnWarningLevel to 'None'.</maml:para>
          <maml:para>This parameter can't be used in addition to the AbortOnWarningLevel parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: IgnoreParserErrors -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreParserErrors</maml:name>
        <maml:description>
          <maml:para>Use this parameter to force the SQL Compare engine to ignore any parser errors.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: SqlCmdVariables -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SqlCmdVariables</maml:name>
        <command:parameterValue required="true">Hashtable</command:parameterValue>
        <dev:type>
          <maml:name>System.Collections.Hashtable</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes />
    <command:returnValues>
      <!-- OutputType: DatabaseSyncResult -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.Domain.DatabaseSyncResult</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$staging = New-DatabaseConnection -ServerInstance "staging01\sql2014" -Database "Staging"
 
Sync-DatabaseSchema -Source $project -Target $staging</dev:code>
        <dev:remarks>
          <maml:para>This example show how to update a database to match a SQL Source Control project.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$buildArtifact = Import-DatabaseBuildArtifact "C:\Work\buildArtifacts\DatabaseBuildArtifact.1.0.0.nupkg"
$production = New-DatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production" -Username "AutomationUser" -Password "P@ssw0rd"
 
Sync-DatabaseSchema -Source $buildArtifact -Target $production</dev:code>
        <dev:remarks>
          <maml:para>This example show how to update a test database to match a SQL Change Automation build artifact.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$validatedProject = Invoke-DatabaseBuild "C:\Work\scripts"
$test = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test" -Username "AutomationUser" -Password "P@ssw0rd"
 
Sync-DatabaseSchema -Source $validatedProject -Target $test</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to update a test database to match a validated SQL Source Control project.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 4 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$test = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test" -Username "AutomationUser" -Password "P@ssw0rd"
 
Sync-DatabaseSchema -Source $project -Target $test -AbortOnWarningLevel Medium</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to abort the update if there are any warnings at medium level or above.</maml:para>
          <maml:para>Set the -AbortOnWarningLevel parameter to 'None' or use the Force parameter if you want the cmdlet to ignore all warnings.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 5 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$test = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test" -Username "AutomationUser" -Password "P@ssw0rd"
 
$syncResult = Sync-DatabaseSchema -Source $project -Target $test
$syncResult.UpdateSql | Out-File -FilePath "C:\Export\update.sql"</dev:code>
        <dev:remarks>
          <maml:para>This example show how to write the updateScript that was run to a file.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 6 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$test = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test" -Username "AutomationUser" -Password "P@ssw0rd"
 
$options = "IgnoreComments, AddObjectExistenceChecks, -ForceColumnOrder"
 
Sync-DatabaseSchema -Source $project -Target $test -SQLCompareOptions $options</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify SQL Compare options to use when performing the sync operation.</maml:para>
          <maml:para>In this example, the $options variable specifies that the IgnoreComments and AddObjectExistenceChecks options should be included in addition to the default set of SQL Compare options. The minus sign before the ForceColumnOrder parameter indicates that this default option will be turned off.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Export-DatabaseTestResults -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Export-DatabaseTestResults</command:name>
      <command:verb>Export</command:verb>
      <command:noun>DatabaseTestResults</command:noun>
      <maml:description>
        <maml:para>Exports a TestResults object to disk.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Export-DatabaseTestResults cmdlet takes a TestResults results object produced by the Invoke-DatabaseTests cmdlet and exports it to a JUnit or MsTest file.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Export-DatabaseTestResults</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The TestResults object to be exported.</maml:para>
          </maml:description>
          <command:parameterValue required="true">TestResults</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaTesting.TestResults</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: OutputFile -->
        <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
          <maml:name>OutputFile</maml:name>
          <maml:description>
            <maml:para>The file path to export the TestResults to.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: Force -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Force</maml:name>
          <maml:description>
            <maml:para>Use this parameter to overwrite any existing file specified by OutputFile.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: Format -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>Format</maml:name>
          <maml:description>
            <maml:para>The format of the TestResults file. This can be JUnit or MsTest.</maml:para>
            <maml:para>If you don't use this parameter, or if you set it to Default, the format will be chosen automatically depending on the file extension of the OutputFile.</maml:para>
            <maml:para>Possible values: Default, JUnit, MsTest</maml:para>
          </maml:description>
          <command:parameterValue required="true">TestResultsFormat</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaTesting.Export.TestResultsFormat</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>Default</dev:defaultValue>
          <command:parameterValueGroup>
            <command:parameterValue required="false" variableLength="false">Default</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">JUnit</command:parameterValue>
            <command:parameterValue required="false" variableLength="false">MsTest</command:parameterValue>
          </command:parameterValueGroup>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The TestResults object to be exported.</maml:para>
        </maml:description>
        <command:parameterValue required="true">TestResults</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaTesting.TestResults</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: OutputFile -->
      <command:parameter required="true" globbing="false" pipelineInput="false" position="named">
        <maml:name>OutputFile</maml:name>
        <maml:description>
          <maml:para>The file path to export the TestResults to.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: Format -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Format</maml:name>
        <maml:description>
          <maml:para>The format of the TestResults file. This can be JUnit or MsTest.</maml:para>
          <maml:para>If you don't use this parameter, or if you set it to Default, the format will be chosen automatically depending on the file extension of the OutputFile.</maml:para>
          <maml:para>Possible values: Default, JUnit, MsTest</maml:para>
        </maml:description>
        <command:parameterValue required="true">TestResultsFormat</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaTesting.Export.TestResultsFormat</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>Default</dev:defaultValue>
        <command:parameterValueGroup>
          <command:parameterValue required="false" variableLength="false">Default</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">JUnit</command:parameterValue>
          <command:parameterValue required="false" variableLength="false">MsTest</command:parameterValue>
        </command:parameterValueGroup>
      </command:parameter>
      <!-- Parameter: Force -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>Force</maml:name>
        <maml:description>
          <maml:para>Use this parameter to overwrite any existing file specified by OutputFile.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaTesting.TestResults</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The TestResults object to be exported.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: None -->
      <command:returnValue>
        <dev:type>
          <maml:name>None</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$testResultsFile = "C:\Export\scripts.junit.xml"
$results = Invoke-DatabaseTests "C:\Work\testproject\AdventureWorks2014.Database.Tests\AdventureWorks2014.Database.Tests.sqlproj"
Export-DatabaseTestResults $results -OutputFile $testResultsFile</dev:code>
        <dev:remarks>
          <maml:para>This example demonstrates the simplest use of Export-DatabaseTestResults with a SQL Change Automation project, only specifying the OutputFile parameter to export the results of the tests to a JUnit file.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$testResultsFile = "C:\Export\scripts.junit.xml"
$results = Invoke-DatabaseTests "C:\Work\Scripts"
Export-DatabaseTestResults $results -OutputFile $testResultsFile</dev:code>
        <dev:remarks>
          <maml:para>This example demonstrates the simplest use of Export-DatabaseTestResults with a SQL Source Control project, only specifying the OutputFile parameter to export the results of the tests to a JUnit file.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$testResultsFile = "C:\Export\scripts.xml"
Invoke-DatabaseTests "C:\Work\testproject\AdventureWorks2014.Database.Tests\AdventureWorks2014.Database.Tests.sqlproj" | Export-DatabaseTestResults -OutputFile $testResultsFile -Format MSTest</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify the format of the test results file. This can be JUnit or MSTest.</maml:para>
          <maml:para>If you don't use the Format parameter, or if you set it to Default, the format will be chosen automatically depending on the file extension of the OutputFile.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 4 ----------</maml:title>
        <dev:code>$testResultsFile = "C:\Export\scripts.junit.xml"
$results = Invoke-DatabaseTests "C:\Work\testproject\AdventureWorks2014.Database.Tests\AdventureWorks2014.Database.Tests.sqlproj"
Export-DatabaseTestResults $results -OutputFile $testResultsFile -Force</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to overwrite an existing test results file using the Force parameter.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Invoke-DatabaseTests -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Invoke-DatabaseTests</command:name>
      <command:verb>Invoke</command:verb>
      <command:noun>DatabaseTests</command:noun>
      <maml:description>
        <maml:para>Runs the tSQLt tests contained in a database project.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Invoke-DatabaseTests cmdlet executes the tSQLt tests contained in a database project. It creates a TestResults object that represents the results of the tests.</maml:para>
      <maml:para>If you use a path to a database project as the input, by default the cmdlet will create a temporary database on LocalDB to run the tests on. Alternatively, you can use the TemporaryDatabaseServer parameter to specify a SQL Server instance to create the temporary database on. This is useful if your database uses features that aren't supported by LocalDB, such as Full-Text Search. If you don't want to use LocalDB and don't have permission to create a database on the SQL Server instance, you can use the TemporaryDatabase parameter to specify an existing database.</maml:para>
      <maml:para>If you use a database connection as the input, the cmdlet will run the tests directly on the specified database.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: TemporaryDatabaseServer -->
      <command:syntaxItem>
        <maml:name>Invoke-DatabaseTests</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The schema to run the tSQLt tests on.</maml:para>
            <maml:para>This can be a scripts folder, a NuGet package or a database connection. This can be:</maml:para>
            <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
            <maml:para>- a database connection string</maml:para>
            <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
            <maml:para>- a build artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
            <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
          </maml:description>
          <command:parameterValue required="true">object</command:parameterValue>
          <dev:type>
            <maml:name>System.Object</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when generating the database to test against.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection or if the value specified is either $null or empty.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>If the SQL Compare engine should ignore parser errors when creating the test database. This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IncludeTestData -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IncludeTestData</maml:name>
          <maml:description>
            <maml:para>Use this parameter to add random data to the test database.</maml:para>
            <maml:para>You can have more control over the data being added, by using the SQLDataGeneratorProject parameter instead.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: QueryBatchTimeout -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>QueryBatchTimeout</maml:name>
          <maml:description>
            <maml:para>The execution timeout, in seconds, for each batch of queries when creating the test database. The default value is 30 seconds for queries and 900 seconds for the test run. A value of zero indicates that no execution timeout will be enforced.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">int</command:parameterValue>
          <dev:type>
            <maml:name>System.Int32</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>30</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: RunOnly -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>RunOnly</maml:name>
          <maml:description>
            <maml:para>Use this parameter to run a specific test or a specific test suite. If you don't use this parameter, every test will be run.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when creating the test database. A default set of options are listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection or if the value specified is either $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>See http://www.red-gate.com/sca/ps/help/compareoptions for a complete list of supported SQL Compare options.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataGeneratorProject -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataGeneratorProject</maml:name>
          <maml:description>
            <maml:para>Use this parameter to specify a SQL Data Generator project file (.sqlgen) that defines the data to be added to the test database.</maml:para>
            <maml:para>To add random data to the test database, use the IncludeTestData parameter instead.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TemporaryDatabaseServer -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TemporaryDatabaseServer</maml:name>
          <maml:description>
            <maml:para>The connection string for the temporary database server used for testing. For example, 'Data Source=TempServer01'.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
            <maml:para>By default, LocalDB is used for the temporary database. However there may be some features in your database that aren't supported by LocalDB (for example, Full-Text Search). In this case, or if LocalDB is not present, use this parameter to specify an alternative SQL Server instance for the temporary database.</maml:para>
            <maml:para>LocalDB is not supported when using a SQL Clone image as a baseline. Therefore, you must specify a temporary database server (or a temporary database). For more information, see http://www.red-gate.com/sca/ps/help/clonebaseline.</maml:para>
            <maml:para>Using this option, SQL Change Automation will create a temporary, randomly-named database on the specified SQL Server instance.</maml:para>
            <maml:para>You can't use this parameter in addition to the TemporaryDatabase parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseServerConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseServerConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
      <!-- Parameter set: TemporaryDatabase -->
      <command:syntaxItem>
        <maml:name>Invoke-DatabaseTests</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The schema to run the tSQLt tests on.</maml:para>
            <maml:para>This can be a scripts folder, a NuGet package or a database connection. This can be:</maml:para>
            <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
            <maml:para>- a database connection string</maml:para>
            <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
            <maml:para>- a build artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
            <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
          </maml:description>
          <command:parameterValue required="true">object</command:parameterValue>
          <dev:type>
            <maml:name>System.Object</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: FilterPath -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>FilterPath</maml:name>
          <maml:description>
            <maml:para>The path to a .scpf filter file.</maml:para>
            <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when generating the database to test against.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection or if the value specified is either $null or empty.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: IgnoreParserErrors -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IgnoreParserErrors</maml:name>
          <maml:description>
            <maml:para>If the SQL Compare engine should ignore parser errors when creating the test database. This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: IncludeTestData -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>IncludeTestData</maml:name>
          <maml:description>
            <maml:para>Use this parameter to add random data to the test database.</maml:para>
            <maml:para>You can have more control over the data being added, by using the SQLDataGeneratorProject parameter instead.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">SwitchParameter</command:parameterValue>
          <dev:type>
            <maml:name>System.Management.Automation.SwitchParameter</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>False</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: QueryBatchTimeout -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>QueryBatchTimeout</maml:name>
          <maml:description>
            <maml:para>The execution timeout, in seconds, for each batch of queries when creating the test database. The default value is 30 seconds for queries and 900 seconds for the test run. A value of zero indicates that no execution timeout will be enforced.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">int</command:parameterValue>
          <dev:type>
            <maml:name>System.Int32</maml:name>
            <maml:uri />
          </dev:type>
          <dev:defaultValue>30</dev:defaultValue>
        </command:parameter>
        <!-- Parameter: RunOnly -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>RunOnly</maml:name>
          <maml:description>
            <maml:para>Use this parameter to run a specific test or a specific test suite. If you don't use this parameter, every test will be run.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Compare options to use when creating the test database. A default set of options are listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection or if the value specified is either $null or empty.</maml:para>
            <maml:para>By default, the following Compare options are used:</maml:para>
            <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
            <maml:para>- DecryptEncryptedObjects</maml:para>
            <maml:para>- DoNotOutputCommentHeader</maml:para>
            <maml:para>- ForceColumnOrder</maml:para>
            <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
            <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
            <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
            <maml:para>- IgnoreUserProperties</maml:para>
            <maml:para>- IgnoreWhiteSpace</maml:para>
            <maml:para>- IgnoreWithElementOrder</maml:para>
            <maml:para>- IncludeDependencies</maml:para>
            <maml:para>- ThrowOnFileParseFailed</maml:para>
            <maml:para>- UseCompatibilityLevel</maml:para>
            <maml:para>See http://www.red-gate.com/sca/ps/help/compareoptions for a complete list of supported SQL Compare options.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataCompareOptions -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataCompareOptions</maml:name>
          <maml:description>
            <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: SQLDataGeneratorProject -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>SQLDataGeneratorProject</maml:name>
          <maml:description>
            <maml:para>Use this parameter to specify a SQL Data Generator project file (.sqlgen) that defines the data to be added to the test database.</maml:para>
            <maml:para>To add random data to the test database, use the IncludeTestData parameter instead.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
        <!-- Parameter: TemporaryDatabase -->
        <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
          <maml:name>TemporaryDatabase</maml:name>
          <maml:description>
            <maml:para>The details of the temporary database used for testing. This can be:</maml:para>
            <maml:para>- a database connection object that contains the connection details for a database. See New-DatabaseConnection for details.</maml:para>
            <maml:para>- a database connection string. For example, 'Data Source=TempServer01;Initial Catalog=TempDatabase01'.</maml:para>
            <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
            <maml:para>By default, LocalDB is used for the temporary database. If you don't want to use LocalDB and don't have permission to create a database on the SQL Server instance, use this option to specify an existing database to use for the temporary copy of the database.</maml:para>
            <maml:para>LocalDB is not supported when using a SQL Clone image as a baseline. Therefore, you must specify a temporary database (or a temporary database server). For more information, see http://www.red-gate.com/sca/ps/help/clonebaseline.</maml:para>
            <maml:para>You can't use this parameter in addition to the TemporaryDatabaseServer parameter.</maml:para>
          </maml:description>
          <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
          <dev:type>
            <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The schema to run the tSQLt tests on.</maml:para>
          <maml:para>This can be a scripts folder, a NuGet package or a database connection. This can be:</maml:para>
          <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
          <maml:para>- a database connection string</maml:para>
          <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
          <maml:para>- a build artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
          <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
        </maml:description>
        <command:parameterValue required="true">object</command:parameterValue>
        <dev:type>
          <maml:name>System.Object</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: IncludeTestData -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IncludeTestData</maml:name>
        <maml:description>
          <maml:para>Use this parameter to add random data to the test database.</maml:para>
          <maml:para>You can have more control over the data being added, by using the SQLDataGeneratorProject parameter instead.</maml:para>
          <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: SQLDataGeneratorProject -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLDataGeneratorProject</maml:name>
        <maml:description>
          <maml:para>Use this parameter to specify a SQL Data Generator project file (.sqlgen) that defines the data to be added to the test database.</maml:para>
          <maml:para>To add random data to the test database, use the IncludeTestData parameter instead.</maml:para>
          <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: RunOnly -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>RunOnly</maml:name>
        <maml:description>
          <maml:para>Use this parameter to run a specific test or a specific test suite. If you don't use this parameter, every test will be run.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TemporaryDatabaseServer -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TemporaryDatabaseServer</maml:name>
        <maml:description>
          <maml:para>The connection string for the temporary database server used for testing. For example, 'Data Source=TempServer01'.</maml:para>
          <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          <maml:para>By default, LocalDB is used for the temporary database. However there may be some features in your database that aren't supported by LocalDB (for example, Full-Text Search). In this case, or if LocalDB is not present, use this parameter to specify an alternative SQL Server instance for the temporary database.</maml:para>
          <maml:para>LocalDB is not supported when using a SQL Clone image as a baseline. Therefore, you must specify a temporary database server (or a temporary database). For more information, see http://www.red-gate.com/sca/ps/help/clonebaseline.</maml:para>
          <maml:para>Using this option, SQL Change Automation will create a temporary, randomly-named database on the specified SQL Server instance.</maml:para>
          <maml:para>You can't use this parameter in addition to the TemporaryDatabase parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseServerConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseServerConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: TemporaryDatabase -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>TemporaryDatabase</maml:name>
        <maml:description>
          <maml:para>The details of the temporary database used for testing. This can be:</maml:para>
          <maml:para>- a database connection object that contains the connection details for a database. See New-DatabaseConnection for details.</maml:para>
          <maml:para>- a database connection string. For example, 'Data Source=TempServer01;Initial Catalog=TempDatabase01'.</maml:para>
          <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
          <maml:para>By default, LocalDB is used for the temporary database. If you don't want to use LocalDB and don't have permission to create a database on the SQL Server instance, use this option to specify an existing database to use for the temporary copy of the database.</maml:para>
          <maml:para>LocalDB is not supported when using a SQL Clone image as a baseline. Therefore, you must specify a temporary database (or a temporary database server). For more information, see http://www.red-gate.com/sca/ps/help/clonebaseline.</maml:para>
          <maml:para>You can't use this parameter in addition to the TemporaryDatabaseServer parameter.</maml:para>
        </maml:description>
        <command:parameterValue required="true">DatabaseConnection</command:parameterValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaSources.DatabaseConnection</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: SQLCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Compare options to use when creating the test database. A default set of options are listed below. To include additional options, specify a comma-delimited list of the option names (eg 'IgnoreComments, AddObjectExistenceChecks'). To turn off a default option, precede the option name with a minus sign (eg '-ForceColumnOrder').</maml:para>
          <maml:para>This parameter will be ignored if the InputObject is a database connection or if the value specified is either $null or empty.</maml:para>
          <maml:para>By default, the following Compare options are used:</maml:para>
          <maml:para>- ConsiderNextFilegroupInPartitionSchemes</maml:para>
          <maml:para>- DecryptEncryptedObjects</maml:para>
          <maml:para>- DoNotOutputCommentHeader</maml:para>
          <maml:para>- ForceColumnOrder</maml:para>
          <maml:para>- IgnoreCertificatesAndCryptoKeys</maml:para>
          <maml:para>- IgnoreDatabaseAndServerNameInSynonyms</maml:para>
          <maml:para>- IgnoreUsersPermissionsAndRoleMemberships</maml:para>
          <maml:para>- IgnoreUserProperties</maml:para>
          <maml:para>- IgnoreWhiteSpace</maml:para>
          <maml:para>- IgnoreWithElementOrder</maml:para>
          <maml:para>- IncludeDependencies</maml:para>
          <maml:para>- ThrowOnFileParseFailed</maml:para>
          <maml:para>- UseCompatibilityLevel</maml:para>
          <maml:para>See http://www.red-gate.com/sca/ps/help/compareoptions for a complete list of supported SQL Compare options.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: SQLDataCompareOptions -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>SQLDataCompareOptions</maml:name>
        <maml:description>
          <maml:para>Specifies the SQL Data Compare options to use when creating the script for validation. To include additional options, specify a comma-delimited list of the option names (eg 'DisableAndReenableDDLTriggers, CompressTemporaryFiles').</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: FilterPath -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>FilterPath</maml:name>
        <maml:description>
          <maml:para>The path to a .scpf filter file.</maml:para>
          <maml:para>Overrides any Filter.scpf file present in the InputObject schema with an alternative filter file to be used when generating the database to test against.</maml:para>
          <maml:para>This parameter will be ignored if the InputObject is a database connection or if the value specified is either $null or empty.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
      <!-- Parameter: QueryBatchTimeout -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>QueryBatchTimeout</maml:name>
        <maml:description>
          <maml:para>The execution timeout, in seconds, for each batch of queries when creating the test database. The default value is 30 seconds for queries and 900 seconds for the test run. A value of zero indicates that no execution timeout will be enforced.</maml:para>
          <maml:para>This parameter will be ignored if the InputObject is a database connection.</maml:para>
        </maml:description>
        <command:parameterValue required="true">int</command:parameterValue>
        <dev:type>
          <maml:name>System.Int32</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>30</dev:defaultValue>
      </command:parameter>
      <!-- Parameter: IgnoreParserErrors -->
      <command:parameter required="false" globbing="false" pipelineInput="false" position="named">
        <maml:name>IgnoreParserErrors</maml:name>
        <maml:description>
          <maml:para>If the SQL Compare engine should ignore parser errors when creating the test database. This parameter will be ignored if the InputObject is a database connection.</maml:para>
        </maml:description>
        <command:parameterValue required="true">SwitchParameter</command:parameterValue>
        <dev:type>
          <maml:name>System.Management.Automation.SwitchParameter</maml:name>
          <maml:uri />
        </dev:type>
        <dev:defaultValue>False</dev:defaultValue>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.Object</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The schema to run the tSQLt tests on.</maml:para>
          <maml:para>This can be a scripts folder, a NuGet package or a database connection. This can be:</maml:para>
          <maml:para>- a Database Connection object created by the New-DatabaseConnection cmdlet</maml:para>
          <maml:para>- a database connection string</maml:para>
          <maml:para>- a path for a NuGet package or .zip file. This must contain a scripts folder located at db\state</maml:para>
          <maml:para>- a build artifact object produced by the New-DatabaseBuildArtifact cmdlet</maml:para>
          <maml:para>- a path for a scripts folder, created by SQL Compare or from your SQL Source Control database repository</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: TestResults -->
      <command:returnValue>
        <dev:type>
          <maml:name>RedGate.Versioning.Automation.Compare.SchemaTesting.TestResults</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$testResults = Invoke-DatabaseTests "C:\Work\testproject\AdventureWorks2014.Database.Tests\AdventureWorks2014.Database.Tests.sqlproj"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Invoke-DatabaseTests cmdlet to run tSQLt tests for a SQL Change Automation project.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 2 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$testResults = Invoke-DatabaseTests $project</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Invoke-DatabaseTests cmdlet to run tSQLt tests for a SQL Source Control project.</maml:para>
          <maml:para>The cmdlet will use LocalDB to run the tests on.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 3 ----------</maml:title>
        <dev:code>$database = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test"
$testResults = Invoke-DatabaseTests $database</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Invoke-DatabaseTests cmdlet to run tSQLt tests already deployed to a database.</maml:para>
          <maml:para>The output will be a TestResults object, which contains the test results.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 4 ----------</maml:title>
        <dev:code>$project = "C:\Work\testproject\AdventureWorks2014.Database.Tests\AdventureWorks2014.Database.Tests.sqlproj"
$testResults = Invoke-DatabaseTests $project -IncludeTestData</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to add random test data before the tests are run.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 5 ----------</maml:title>
        <dev:code>$project = "C:\Work\scripts"
$testResults = Invoke-DatabaseTests $project -SqlDataGeneratorProject 'C:\Work\DataGeneratorProject.sqlgen'</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to add test data defined by a SQL Data Generator project file (.sqlgen).</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 6 ----------</maml:title>
        <dev:code>$scriptsFolder = "C:\Work\scripts"
$testResults = Invoke-DatabaseTests $scriptsFolder -RunOnly "[SQLCop].[test Unnamed Constraints]"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to run the single test "[SQLCop].[test Unnamed Constraints]".</maml:para>
          <maml:para>To run all tests in a single test suite, use the RunOnly parameter to specify the name of the test suite. For example: "[SQLCop]".</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 7 ----------</maml:title>
        <dev:code>$project = "C:\Work\testproject\AdventureWorks2014.Database.Tests\AdventureWorks2014.Database.Tests.sqlproj"
$testResults = $project | Invoke-DatabaseTests -TemporaryDatabaseServer "Data Source=temp01\sql2014"</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify a SQL Server instance for the temporary database, instead of using LocalDB.</maml:para>
          <maml:para>This is useful if you don't want to use LocalDB because your database uses features that aren't supported by LocalDB, such as Full-Text Search.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 8 ----------</maml:title>
        <dev:code>$project = "C:\Work\testproject\AdventureWorks2014.Database.Tests\AdventureWorks2014.Database.Tests.sqlproj"
$temporaryDatabase = New-DatabaseConnection -ServerInstance "temp01\sql2014" -Database "TemporaryDb"
$testResults = $project | Invoke-DatabaseTests -TemporaryDatabase $temporaryDatabase</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify an existing SQL Server database to use as the temporary database, instead of using LocalDB.</maml:para>
          <maml:para>This is useful if you don't want to use LocalDB and you don't have permission to create a database on the SQL Server instance.</maml:para>
        </dev:remarks>
      </command:example>
      <command:example>
        <maml:title>---------- EXAMPLE 9 ----------</maml:title>
        <dev:code>$project = "C:\Work\testproject\AdventureWorks2014.Database.Tests\AdventureWorks2014.Database.Tests.sqlproj"
$options = "IgnoreComments, AddObjectExistenceChecks, -IgnoreUserProperties"
$testResults = $project | Invoke-DatabaseTests -SQLCompareOptions $options</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to specify SQL Compare options to use when creating the test database.</maml:para>
          <maml:para>In this example, the $options variable is used to specify that the IgnoreComments and AddObjectExistenceChecks options should be included in addition to the default set of SQL Compare options used by this cmdlet. The minus sign before IgnoreUserProperties indicates that this default option will be turned off.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Get-DependentProjectPaths -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Get-DependentProjectPaths</command:name>
      <command:verb>Get</command:verb>
      <command:noun>DependentProjectPaths</command:noun>
      <maml:description>
        <maml:para>Retrieves all SQL Change Automation projects in dependency order within a folder.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>The Get-DependentProjectPaths cmdlet searches a folder for SQL Change Automation projects and returns their file paths in the order in which they ought to be built.</maml:para>
      <maml:para>The folder specified should normally be a folder containing a solution file.</maml:para>
      <maml:para>Dependency evaluation takes into account both dependencies defined between projects, and dependencies defined in the solution file.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Get-DependentProjectPaths</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The path to the folder containing database projects.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The path to the folder containing database projects.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The path to the folder containing database projects.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: IReadOnlyCollection`1 -->
      <command:returnValue>
        <dev:type>
          <maml:name>System.Collections.Generic.IReadOnlyCollection`1[[RedGate.Versioning.Automation.EngineFacade.Dependencies.OrderedProject, RedGate.Versioning.Automation.EngineFacade, Version=4.3.21062.24481, Culture=neutral, PublicKeyToken=7f465a1c156d4d57]]</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>$projectFolderPath = "C:\Work\project"
$projectFiles = $projectFolderPath | Get-DependentProjectPaths
$projectFiles | ForEach-Object {
    $projectFile = $_.FilePath
    $validatedProject = $projectFile | Invoke-DatabaseBuild
}</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to use the Get-DependentProjectPaths in conjunction with the Invoke-DatabaseBuild cmdlet to build multiple SQL Change Automation projects.</maml:para>
          <maml:para>It is also possible to deploy projects to databases on a temporary server so that cross-database dependencies can be handled</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Register-SqlChangeAutomation -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Register-SqlChangeAutomation</command:name>
      <command:verb>Register</command:verb>
      <command:noun>SqlChangeAutomation</command:noun>
      <maml:description>
        <maml:para>Activates SQL Change Automation using a valid serial number.</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>To find your serial number, check your invoice or go to https://www.red-gate.com/myserialnumbers.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Register-SqlChangeAutomation</maml:name>
        <!-- Parameter: InputObject -->
        <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
          <maml:name>InputObject</maml:name>
          <maml:description>
            <maml:para>The SQL Change Automation serial number.</maml:para>
          </maml:description>
          <command:parameterValue required="true">string</command:parameterValue>
          <dev:type>
            <maml:name>System.String</maml:name>
            <maml:uri />
          </dev:type>
        </command:parameter>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters>
      <!-- Parameter: InputObject -->
      <command:parameter required="true" globbing="false" pipelineInput="true (ByValue)" position="0">
        <maml:name>InputObject</maml:name>
        <maml:description>
          <maml:para>The SQL Change Automation serial number.</maml:para>
        </maml:description>
        <command:parameterValue required="true">string</command:parameterValue>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
      </command:parameter>
    </command:parameters>
    <command:inputTypes>
      <command:inputType>
        <dev:type>
          <maml:name>System.String</maml:name>
          <maml:uri />
        </dev:type>
        <maml:description>
          <maml:para>The SQL Change Automation serial number.</maml:para>
        </maml:description>
      </command:inputType>
    </command:inputTypes>
    <command:returnValues>
      <!-- OutputType: None -->
      <command:returnValue>
        <dev:type>
          <maml:name>None</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>Register-SqlChangeAutomation 048-001-224164-5B49</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to activate SQL Change Automation using a SQL Change Automation serial number.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
  <!-- Cmdlet: Unregister-SqlChangeAutomation -->
  <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10">
    <command:details>
      <command:name>Unregister-SqlChangeAutomation</command:name>
      <command:verb>Unregister</command:verb>
      <command:noun>SqlChangeAutomation</command:noun>
      <maml:description>
        <maml:para>Deactivates SQL Change Automation</maml:para>
      </maml:description>
    </command:details>
    <maml:description>
      <maml:para>This unregisters a SQL Change Automation serial number previously registered on this machine.</maml:para>
    </maml:description>
    <command:syntax>
      <!-- Parameter set: __AllParameterSets -->
      <command:syntaxItem>
        <maml:name>Unregister-SqlChangeAutomation</maml:name>
      </command:syntaxItem>
    </command:syntax>
    <command:parameters />
    <command:inputTypes />
    <command:returnValues>
      <!-- OutputType: None -->
      <command:returnValue>
        <dev:type>
          <maml:name>None</maml:name>
          <maml:uri />
        </dev:type>
      </command:returnValue>
    </command:returnValues>
    <command:examples>
      <command:example>
        <maml:title>---------- EXAMPLE 1 ----------</maml:title>
        <dev:code>Unregister-SqlChangeAutomation</dev:code>
        <dev:remarks>
          <maml:para>This example shows how to deactivate SQL Change Automation.</maml:para>
        </dev:remarks>
      </command:example>
    </command:examples>
  </command:command>
</helpItems>