microsoft / dwscripter Goto Github PK

DWScripter is a scripting tool for Analytics Platform System and Azure SQLDW. This Console app will script the ddl and dml for both APS and SQLDW.

License: MIT License

C# 100.00%

dwscripter's Introduction

Introduction

DWScripter is a scripting tool for Analytics Platform System and Azure SQLDW. This Console app will script the ddl and dml for both APS and SQLDW. Supports: PDW V2, Azure SQLDW, DDL and DML, schemas (version 2.4)

The project is intended as a cross platform tool, and as such is built on .NET Core SDK 2.0.2. You can build the solution and run the tool from the OS of your choice.

Requirements

PDWScripter requires Newtonsoft.json version 10.0.3 or above. You will need to add the package to your system. For more information and samples on how to add the package see Newtonsoft.json NuGet page.

Getting Started

Dowload the sources and build DWScripter tool. For building instructions see How To Contribute

The Solution contains two projects:

PDWScripter
DWScripter

PDWScripter is a class library project, made with the purpose of being reusable in custom projects to provide the Data Warehouse object scripting capability. For more information on using the library in your projects, please refer to PDWScripter How To and to PDWScripter License DWScripter is a console application that makes use of the PDWScripter library

DWScripter requires some paramters to identify the instance and databases to be scripted, as well as the object (DML, DDL or both).

You must invoke DWScripter passing all the required parameters. For more information on the tool usage see Usage

Current version is 1.1.0

See ChangeLog

USAGE

For more information on the tool usage see Usage

Contributing

If you are interested in fixing issues and contributing directly to the code base please see contributing guidelines

Please also review our Code of Conduct.

Reporting Security Issues

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

dwscripter's People

Contributors

Stargazers

Watchers

Forkers

dsabella84 alexgay jackwagons vdedyukhin bhaskers-blu-org2 taffywrinkle claudiusgonzo kmatt keranem1 marmikreal

dwscripter's Issues

Partitioned non-CCI tabels wrong clustered index definition

Expected Behavior

non-CCI partitioned tables with clustered index should only show the user created indexes

Actual Behavior

non-CCI partitioned tables with clustered indexes are scripted with an extra clustered index on the partition column

Steps to reproduce the behavior

Create a non-CCI partitioned table with a clustered index:
CREATE TABLE [Clustered_Partitioned] ( [INT_NO] INT NOT NULL, [DEV_NO] VARCHAR(10) NOT NULL, [DATE_NO] INT NOT NULL ) WITH (DISTRIBUTION=HASH(INT_NO), CLUSTERED INDEX ( [DEV_NO] ASC), PARTITION ([DATE_NO] RANGE LEFT FOR VALUES (20010101,20020101)))
Scripting this object will report:
CREATE TABLE [dbo].[Clustered_Partitioned] ( [INT_NO] int NOT NULL ,[DEV_NO] varchar (10) COLLATE Latin1_General_100_CI_AS_KS_WS NOT NULL ,[DATE_NO] int NOT NULL ) WITH ( DISTRIBUTION = HASH ([INT_NO]) , CLUSTERED INDEX ([DATE_NO]CLUSTERED INDEX ([DEV_NO]) , PARTITION ([DATE_NO] RANGE LEFT FOR VALUES (N'20010101' ,N'20020101')));
with the extra CLUSTERED INDEX on DATE_NO

Project Version

1.0.0

OS details

ALL

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Exception thrown on Names with \

Expected Behavior

Create the script file

Actual Behavior

Throws an exception due to file name has a backslash contained in schema name.

Steps to reproduce the behavior

create a schema with a backslash, for example MSFT\dsabella.test, this will throw an exception when attempting to write the file due to it expecting another folder to be created for this file. Possible solution would be to just replace this in the filename with a character of _

Running this using the APS migration tool through powershell

Project Version

Beta

OS details

Win 10

timeout while scripting FULL database

Expected Behavior

execution should complete without errors

Actual Behavior

Execution aborts with time out error

Steps to reproduce the behavior

Run DWScripter with -M:FULL to script entire database against a database with high number of objects, tables with high number of partitions or unhealthy CCI tables

Project Version

1.0.0

OS details

ALL supported

microsoft / dwscripter Goto Github PK

dwscripter's Introduction

Introduction

Requirements

Getting Started

Current version is 1.1.0

USAGE

Contributing

Reporting Security Issues

dwscripter's People

Contributors

Stargazers

Watchers

Forkers

dwscripter's Issues

Expected Behavior

Actual Behavior

Steps to reproduce the behavior

Project Version

OS details

Expected Behavior

Actual Behavior

Steps to reproduce the behavior

Project Version

OS details

Expected Behavior

Actual Behavior

Steps to reproduce the behavior

Project Version

OS details

Recommend Projects

Recommend Topics

Recommend Org