2016-04-22
1,046 reads
2016-04-22
1,046 reads
The SSIS Script Task allows you to add functionality to your SSIS package that does not already exist with the other predefined tasks. In this article, Daniel Calbimonte looks at how to get started using the SSIS Script Task with a few examples.
2016-03-30
4,402 reads
As you develop, test and deploy SSIS packages, you need to specify different parameter values for things like database connection strings, file and folder paths, etc. without having to edit the individual SSIS packages to make these changes. Ray Barley looks at how you can accomplish this goal by taking advantage of the configuration capabilities that SSIS provides, in particular the SQL Server package configuration.
2016-03-21
5,914 reads
2016-03-16
1,042 reads
An SSIS package that is executed on an ad hoc basis can be run from Business Intelligence Development Studio easily enough, but a package that is going to be run on a regular schedule is best executed through a batch file using the DTExec.exe command line utility.
2018-08-31 (first published: 2016-03-14)
102,336 reads
2016-03-01
1,245 reads
Because SSIS is case sensitive, random VS_NEEDSNEWMETADATA errors on case-insensitive databases may indicate issues in your database change management & deployment process.
2016-02-11
2,439 reads
Read this tip to learn how to import data from multiple Excel worksheets into SQL Server using SSIS.
2016-02-05
4,291 reads
Demo and script on how to script out SSIS Environments and their associated variables
2018-03-02 (first published: 2016-01-21)
29,393 reads
2015-10-23
1,444 reads
By Steve Jones
Thanks to everyone who attended my sessions today at SQL Saturday Boston 2025. I’ve...
SQL Server 2025 introduces native support for vector data types and external AI models....
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
Comments posted to this topic are about the item Building AI Governance and Policies-...
Why is sql doing a full scan VS seeking on the index? I've included...
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9 GO DBCC CHECKIDENT(TravelLog, RESEED) GO INSERT dbo.TravelLog ( CityID, StartDate, EndDate ) VALUES (4, '2025-09-14', '2025-09-17') GOWhat is the identity value for the new row inserted by the insert statement above? See possible answers