<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SSIS Talk &#187; SSIS Feature Request</title>
	<atom:link href="http://www.ssistalk.com/category/ssis/ssis-feature-request/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ssistalk.com</link>
	<description>Random thoughts and experiences with SSIS, by Phil Brammer</description>
	<lastBuildDate>Wed, 01 Feb 2012 12:48:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>SSIS &#8211; Feature Request: Snap-To Guides</title>
		<link>http://www.ssistalk.com/2011/02/17/ssis-feature-request-snap-to-guides/</link>
		<comments>http://www.ssistalk.com/2011/02/17/ssis-feature-request-snap-to-guides/#comments</comments>
		<pubDate>Thu, 17 Feb 2011 18:55:15 +0000</pubDate>
		<dc:creator>Phil Brammer</dc:creator>
				<category><![CDATA[SSIS]]></category>
		<category><![CDATA[SSIS Feature Request]]></category>

		<guid isPermaLink="false">http://www.ssistalk.com/?p=248</guid>
		<description><![CDATA[Have you ever designed an SSIS package and wished that you had easier layout tools?  Ever wanted the snap-to guides that allow you to position tasks/components in such a way that they align with existing tasks/components on the design surface?  
Here&#8217;s what I&#8217;m referring to (note the blue dashed line on the left):

Well, [...]]]></description>
			<content:encoded><![CDATA[<p>Have you ever designed an SSIS package and wished that you had easier layout tools?  Ever wanted the snap-to guides that allow you to position tasks/components in such a way that they align with existing tasks/components on the design surface?  </p>
<p>Here&#8217;s what I&#8217;m referring to (note the blue dashed line on the left):<br />
<img src="http://www.ssistalk.com/SSIS_SnapTo.png" alt="SSIS Snap-To Guide Lines" /></p>
<p>Well, now&#8217;s your chance &#8211; please <a href="https://connect.microsoft.com/SQLServer/feedback/details/644668/ssis-snap-to">vote</a> for <a href="http://sqlblog.com/blogs/jamie_thomson/">Jamie Thomson&#8217;s</a> suggestion to add this feature to SSIS.  While there, please be sure to leave feedback as to why you would like to see this included.</p>
<p>Vote here: <a href="https://connect.microsoft.com/SQLServer/feedback/details/644668/ssis-snap-to">https://connect.microsoft.com/SQLServer/feedback/details/644668/ssis-snap-to</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ssistalk.com/2011/02/17/ssis-feature-request-snap-to-guides/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>SSIS &#8211; Feature Request: Option to mark connection managers read-only</title>
		<link>http://www.ssistalk.com/2010/01/19/ssis-feature-request-option-to-mark-connection-managers-read-only/</link>
		<comments>http://www.ssistalk.com/2010/01/19/ssis-feature-request-option-to-mark-connection-managers-read-only/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 20:39:35 +0000</pubDate>
		<dc:creator>Phil Brammer</dc:creator>
				<category><![CDATA[SSIS]]></category>
		<category><![CDATA[SSIS Feature Request]]></category>

		<guid isPermaLink="false">http://www.ssistalk.com/?p=200</guid>
		<description><![CDATA[Today I had a situation come up that prompted a SQL Server Connect feature request submission for SSIS: add the ability to mark a connection manager object as read-only.  In doing so, the connection manager would not show in dataflow destinations, it would throw a warning if added to an OLE DB Command component, [...]]]></description>
			<content:encoded><![CDATA[<p>Today I had a situation come up that prompted a <a href="https://connect.microsoft.com/SQLServer/feedback">SQL Server Connect</a> feature request submission for SSIS: add the ability to mark a connection manager object as read-only.  In doing so, the connection manager would not show in dataflow destinations, it would throw a warning if added to an OLE DB Command component, would error in package validation if used in a destination (which could happen post-development via config files), etc&#8230;</p>
<p>What do you think?  Is this something you could see value in having implemented?</p>
<p>Connect submission: <a href="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=525805">https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=525805</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ssistalk.com/2010/01/19/ssis-feature-request-option-to-mark-connection-managers-read-only/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

