<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results for 'app:weblogs' matching tag 'scheduled'</title><link>http://msmvps.com/search/SearchResults.aspx?q=app:weblogs&amp;tag=scheduled&amp;orTags=0&amp;o=DateDescending</link><description>Search results for 'app:weblogs' matching tag 'scheduled'</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>SSIS Error: Text was truncated or one or more characters had no match in the target code page</title><link>/http://sqlserver-qa.net/blogs/tools/archive/2007/08/29/ssis-error-text-was-truncated-or-one-or-more-characters-had-no-match-in-the-target-code-page.aspx</link><pubDate>Wed, 29 Aug 2007 05:00:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1145644</guid><dc:creator>Anonymous</dc:creator><description>This error started generating since last 2 days on a scheduled job that uses SSIS to import content from a flat file. Eventually we found that a derived column within the table and the flat file flow where dates in YYYYMMDD are changed to MM/DD/YYYY format. Then the string MM/DD/YYYY is converted to a date in a Data Conversion flow. And finally the data is put into a SQL Server table (currently with no rows). There is a temparory table involved here to import rows and then eventually the relevant...(&lt;a href="http://sqlserver-qa.net/blogs/tools/archive/2007/08/29/ssis-error-text-was-truncated-or-one-or-more-characters-had-no-match-in-the-target-code-page.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=1774" width="1" height="1" alt="" /&gt;</description></item><item><title>Delete DEMO alerts from SQLAgent</title><link>/http://sqlserver-qa.net/blogs/tools/archive/2007/05/25/delete-demo-alerts-from-sqlagent.aspx</link><pubDate>Fri, 25 May 2007 05:00:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:925380</guid><dc:creator>Anonymous</dc:creator><description>Since the days of SQL 70 automated administrative tasks are getting better with the usage of SQLAgent, you need to know how to configure alerts and set up operators, the people SQL Server contacts when alert conditions arise. SQLAgent Jobs can trigger alerts, for example, when a scheduled job fails or when a log file fills up. You can also define alerts to trigger jobs in response to an alert condition. By default SQL Server will get installed with Demo alerts and you can leave them as it is or drop...(&lt;a href="http://sqlserver-qa.net/blogs/tools/archive/2007/05/25/delete-demo-alerts-from-sqlagent.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlserver-qa.net/aggbug.aspx?PostID=550" width="1" height="1" alt="" /&gt;</description></item></channel></rss>