New answers tagged

0

you can split a large text to smaller chunks, in the rows and load them in foreach loop container, Declare @maxRowLength int = 50; with x as ( select 'Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry''s standard dummy text ever since the 1500s. Over the years, sometimes by accident, sometimes on ...


0

You can use a script transformation to create the actual column mapping. For your flat file source, make every output line become a single large column. In your script transformation, create column definitions for each column you need mapped / already know about. This assumes your first line contains headers: Then, in your script transformation , split ...


0

Just solved that issue myself, your SQL server is missing a few features that's why SSISDBBakup.bak file is missing, it should be under: C:\Program Files\Microsoft SQL Server\120\DTS\Binn\SSISDBBackup.bak Install SQL Integration Services Feature and it will work. /Burim


0

According to this and this, there are upgrades to the sqlcmd.exe utility that I am assuming are reflective of underlying changes in the libraries. For instance, Beginning in the ODBC Driver 11 for SQL Server, there is no limit on the amount of data that retrieved in a single column when –y0 is specified. I realize that this says the ODBC driver, but ...


1

Not sure if you ever got this solved, but I was able to find it in the GAC: C:\Windows\assembly\GAC_MSIL\Microsoft.DataTransformationServices.Controls\...\Microsoft.DataTransformationServices.Controls.DLL Let me know if that did the trick for you


1

Sounds like you are interested in computed columns, https://msdn.microsoft.com/en-us/library/ms188300.aspx. The final column, InventoryValue is computed based on the QtyAvailable and UnitPrice columns. CREATE TABLE dbo.Products ( ProductID int IDENTITY (1,1) NOT NULL , QtyAvailable smallint , UnitPrice money , InventoryValue AS QtyAvailable * ...


2

Check the blog post I wrote on SQLServer.science concerning how to identify this S-1-9 SID. From that post: This can happen as a result of using EXECUTE AS USER = 'SomeUser'; to switch context to another user that doesn’t have a server-level account. I imagine you'd see this exact scenario for contained users. There is also an MSDN post from 2006 ...


0

For date key you might prefer a number. So for April 7th 2016 201604 (Or 20160407 in case of extended requirements) might be best for your date. I don't think that in a DW you need an IDENTITY column for a primary key; After all, you're more aggregating then asking to see a specific value. What I do is make sure the index avoids duplication of values: for ...



Top 50 recent answers are included