SQL Server SSIS : List Of All System Variables And Their Scope (on MSDN)

The Prize $50.00 gift card and a certified certificate for the world’s largest package.

For more details and to enter the contest, head over to Brian Knight’s blog post on this topic here.

Unlike Database connections strings, where the entire connection information is represented by a single string delimited with a semi-colon, the FTP ConnectionString property in SSIS consists of only the FTP Server Name and the Port Number, ex: ftp.yourftpserver.com:21

So what happens if you specify values for both the ConnectionString, as well as the ServerName and ServerPort properties for your FTP Connection Manager in Config File ?

I have tested the 3 separate scenarios and found that the precendence is as follows.

1. ConnectionString property as well as ServerName and ServerPort are populated

SSIS will use the combination of ServerName and ServerPort values and ignore the ConnectionString property value.

2. ServerName and ServerPort only are populated, ConnectionString property is not populated,

SSIS will use the value in the ConnectionString property.

3. ConnectionString property only is populated, ServerName and ServerPort are not populated

SSIS will use the value in the ConnectionString property.

So in 2 out of the 3 cases, SSIS uses the ServerName and ServerPort property values. In other words, if the ServerName and ServerPort properties are populated, it is given higher precence than the value in the ConnectionString property (even if populated).

Photo Credit: Graham Ballantyne – Phil Schiller introduces Bare Naked Ladies @ 2008 Beer Bash

If you are still not convinced, take a look at the comments on this article, which are likely amongst the best dialogues ever seen between the two waring factions (The cool “Mac Guys” / “Fan Boys” and the dorky, but RICH and hence powerful “PC Guys”).

For example, Doug says…

Mac proselytizers remind me of Scientologists. Both have about the same grasp on reality and pretty much identical delusions of self importance.

Posted by: doug | Dec 22, 2008 3:47:00 PM

then Andy says…

Wait…Apple customers were special? : )

Posted by: Andy | Dec 22, 2008 3:09:59 PM

then Ian says

Apple users are still very special people.

They take DRM and smile, they take features being withdrawn and smile.

they lick the windows… and smile.

very SPECIAL.

Posted by: ian | Dec 22, 2008 3:29:41 PM

then Pete says

Mullets are now so LEADING edge! If they were in fashion then they wouldn’t be cool.

Posted by: Pete B | Dec 22, 2008 5:03:37 PM

then Paul says

Tee Hee. Wind up the fanboys and watch them dance.

Can you do Linux and Microsoft for the next two?

Posted by: Paul G | Dec 22, 2008 5:22:01 PM

and finally Matt says…

Jesus.

Posted by: Matt | Dec 22, 2008 6:03:47 PM

It is worth mentioning that the PC still owns 95% of the computer software market and yes, Bill is still likely laughing his A$$ off @ Steve (and his “fan boys”) !

So in the end, the Apple “Fans Boys” are left with nothing more than a cult with an increasingly tired audience and waning popularity.

Further Reading

• Finally! Say good-bye to Apple fanboys.
• The Thin Skin of Apple Fans – NYTimes.com

So before running this sample code, remember to run the update query to update 2 of the rows with time values, so that you can see that this query actually works. Also remember to change the datetime format number (Ex 101 for US dates) in the CONVERT methods in the SQL before using it in your code.

Update 2 Rows With Time value For Testing The Select Query

use AdventureWorks
go

-- update 2 rows with time to test the select query
update Sales.SalesTerritory set ModifiedDate = '1998-06-01 17:30:06.000' where TerritoryID = 2
update Sales.SalesTerritory set ModifiedDate = '1998-06-01 18:35:11.000' where TerritoryID = 3

Query To Select Rows Based On Time Only – US Date Format

use AdventureWorks
go

-- select only those territories whose modified time on 6/1/1998 was after 5:30 pm (date in US format)
declare @checkDateTime DATETIME
select @checkDateTime  = CONVERT(DateTime, CONVERT(Char, '6/1/1998', 101), 101) + convert(datetime, '17:30:00',114)
select ModifiedDate, * from Sales.SalesTerritory where  ModifiedDate  >= @checkDateTime

Query To Select Rows Based On Time Only – British / UK Date Format

use AdventureWorks
go

-- select only those territories whose modified time on 1/6/1998 was after 5:30 pm (date in our beloved queen's format)
declare @checkDateTime DATETIME
select @checkDateTime  = CONVERT(DateTime, CONVERT(Char, '1/6/1998', 103), 103) + convert(datetime, '17:30:00',114)
select ModifiedDate, * from Sales.SalesTerritory where  ModifiedDate  >= @checkDateTime

If you want to do it for the current date, replace the hardcoded date value in the example with GETDATE() Likewise, if you want to do it for yesterdays date, or the day before yesterday, use GETDATE() – 1 or GETDATE() – 2 respectively.

Very simple and neat implementation. Link to download the package is at the bottom of the article. The package is free to download, but forces you to register for free on the download DNN site.

The idea is to rescue “SQL Server Gal” who is trapped by some robot virus. In order to do that, you crack a 15 character code, 7 of which are already highlighted in green on the welcome page, and the remaining 8 of which will be awarded to you if you successfully complete the 8 SQL Server 2008 developer fundamentals course online.

The various training sessions available for free are as follows

• Uncovering T-SQL on SQL Server 2008 ( Part 1 )
• Working with unstructured data in SQL Server 2008 ( Part 2 )
• Working with asynchronous data in SQL Server 2008 ( Part 3 )
• Deploying managed code to SQL Server 2008 ( Part 4 )
• Developing for SQL Server 2008 using Visual Studio ( Part 5 )
• SQL Server 2008 and ADO.Net entity framework integration ( Part 6 )
• Communicating with SQL Server 2008 using HTTP ( Part 7 )
• Working with SQL Server 2008 and disconnected clients ( Part 8 )

The training sessions are provided by ISV Innovation.

Today, it appears to have crossed that landmark and is standing tall at 108,531. That is an average of over 25,000 tech jobs every month so far !

The Federal WARN Act (The Worker Adjustment and Retraining Notification Act) requires most employers to give a 60 days notice of impending layoffs.  That coupled with some companies announcing their layoffs on their company blogs makes me trust this tracker to be fairly accurate for tracking tech job losses in Depression 2.0.

Of course, there will always be a margin of error, in part, caused by tech firms that defy such laws and cut jobs without warning (March 2001).