Hot answers tagged

6

Honestly, you shouldn't be editing the package to point to another environment before deploying it. Please look into package configurations to learn about methods to deploy your packages without editing the package itself. Likely your connection strings and other settings should just be a variable read from a configuration file. Since you are using SQL ...


4

The biggest number you can fit into numeric(5,2) is 999.99. Therefore 123.556... is fine, but 1234.556... is too big. You can find the rules for truncation, rounding, and errors during implicit conversions in the documentation: CAST and CONVERT (Transact-SQL) I don't know SQL-server that well, so I don’t know if you can configure the behaviour. One idea ...


4

I can watch the database size grow from 2GB to 12GB (max space available) where it runs out of space and returns the following message: The issue is either you're simply running out of disk space and the physical file cannot grow to complete the transaction, or you have a limit on the SQL file growth settings and the physical file cannot grow more ...


3

I had similar issue before with my SQL Server 2012 Enterprise Edition production box. Even though I would make sure everything was refreshed under SSIS packages before I deployed to the production box, when it executed on the production box it would just not work, saying object doesn't exists. I also had all the validation turned on, but that didn't help. ...


3

I was not able to reproduce your error (although I only tested with one table in the mix). An OLE DB Destination has the ability to disable trigger and other check constraints when it loads but the OLE DB Command does not provide a similar facility. Set up I created a simplistic table --- a key, a value and an empty field that will be populated, via ...


2

For posterity I got this working via the following: Altering the sproc called by the users (Admin.RunImport) to 'Execute as' the account used by the SQL Service. The Sql service account (an AD Managed Service account) is modified to have permissions to execute the Admin sproc allowing the use of execute as above The Sql service account is modified to have ...


2

It looks like your installation of Visual Studio 2015 registered itself as the editor for script task instead of what it was before. What you need to do is make sure the right editor is used again to edit script components. You could get away with re-registering the correct components for use with script tasks, but it could be needed to remove some ...


2

Based on clarification from the comments, the work flow was C:\SourceFolder\File1.csv -> C:\SourceFolder\Archive\File1.csv The ForEach File Enumerator has a Traverse Subfolder option which allows the enumerator to look beyond the top level of a folder hierarchy. The specific mechanics of how the enumerator appears to be implemented is that it will ...


1

Since you're using 2012+, you have windowing functions available to you which I think make this easier to solve. Here's my set up. IF NOT EXISTS ( SELECT * FROM sys.tables AS T INNER JOIN sys.schemas AS S ON s.schema_id = t.schema_id WHERE S.name ='dbo' AND T.name = 'StagingBenefit' ) BEGIN ...


1

Since you are getting the error when saving and not executing the package, you are using SQL 2014 you are probably being bitten by the new security features introduced in 2012. Your user's login most likely doesn't have access to the SSISDB catalog (even though he might have access to SQL Server). You need to map the login to an SSISDB user and configure ...


1

The following will show you if the triggers are enabled. If they are, they will fire, assuming the DML meets the trigger requirements. You should run this while the SSIS package is running. SELECT TableName = QUOTENAME(s.name) + '.' + QUOTENAME(o.name) , TriggerName = t.name , t.is_disabled FROM sys.triggers t INNER JOIN sys.objects o ON ...



Only top voted, non community-wiki answers of a minimum length are eligible