<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Developer hearted / Relational minded</title><subtitle type="html" /><id>http://blogs.msdn.com/jenss/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/jenss/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2009-09-18T22:22:00Z</updated><entry><title>Want to know what happened on your database by reading the transaction log ?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/11/18/want-to-know-what-happened-on-your-database-by-reading-the-transaction-log.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/11/18/want-to-know-what-happened-on-your-database-by-reading-the-transaction-log.aspx</id><published>2009-11-18T09:23:39Z</published><updated>2009-11-18T09:23:39Z</updated><content type="html">(Download the dbo.fndblog2 function here ) Update and word of caution: Be aware that &amp;#160; the mentioned function is undocumented and subject to change in any release of SQL Server. You should only use that for investigational purposes and in case you are investigating any sever data issues on your server. The function will parse the logs and might cause (depending on the size of the log) a severe impact on performance while running. In various situations you will not be able to either use third...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/11/18/want-to-know-what-happened-on-your-database-by-reading-the-transaction-log.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9924190" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author></entry><entry><title>An “secret” SSIS XML Destination Provider you might not found yet</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/11/06/an-secret-ssis-xml-destination-provider-you-might-not-found-yet.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/11/06/an-secret-ssis-xml-destination-provider-you-might-not-found-yet.aspx</id><published>2009-11-06T13:16:14Z</published><updated>2009-11-06T13:16:14Z</updated><content type="html">&amp;#160; (Sample code included at the end of the post) The initiator for this post was Dan Atkins who wanted to create a feed from relational data to consume it directly from a created gadget. Where can I find that in the toolbox ? First of all, you won’t a XML destination adapter as of the shipped components in SQL Server 2005 and 2008. There are for sure third party components which can directly convert data from the data pipeline to defined XML but sometimes it is much easier than that and you just...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/11/06/an-secret-ssis-xml-destination-provider-you-might-not-found-yet.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9918561" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx" /><category term="XML" scheme="http://blogs.msdn.com/jenss/archive/tags/XML/default.aspx" /><category term="SSIS" scheme="http://blogs.msdn.com/jenss/archive/tags/SSIS/default.aspx" /></entry><entry><title>SSIS as a data source needed ? Watch out for configuration traps</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/10/26/ssis-as-a-data-source-needed-watch-out-for-configuration-traps.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/10/26/ssis-as-a-data-source-needed-watch-out-for-configuration-traps.aspx</id><published>2009-10-26T20:27:57Z</published><updated>2009-10-26T20:27:57Z</updated><content type="html">&amp;#160; Someone pinged me according the article I wrote about SSIS as a data source in Reporting Services. In general this is easy to implement and configure. One problem though occurs if you already had SQL Server 2005 on the machine first and updated to SQL Server 2008. You will receive the following error: The data processing extension used for this report is not available. It has either been uninstalled, or it is not configured correctly. According to the configuration file RSReportServcer.config,...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/10/26/ssis-as-a-data-source-needed-watch-out-for-configuration-traps.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9913165" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx" /><category term="XML" scheme="http://blogs.msdn.com/jenss/archive/tags/XML/default.aspx" /><category term="SSIS" scheme="http://blogs.msdn.com/jenss/archive/tags/SSIS/default.aspx" /></entry><entry><title>SQLIOSIMParser 0.3.3.0 is available</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/10/23/sqliosimparser-0-3-3-0-is-available.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/10/23/sqliosimparser-0-3-3-0-is-available.aspx</id><published>2009-10-23T10:56:47Z</published><updated>2009-10-23T10:56:47Z</updated><content type="html">After skipping some internal version the 0.3.3.0 is available now , these are the new features: Version 0.3.1.0 &amp;lt;Internal Bugfixing&amp;gt; Version 0.3.3.0 -Moved settings to a separate settings page and save them for later use (Suggested by me) -Added additionally feedback options (Feedback by me) Feel free to provide feedback to either the new feedback functionality or the discussion list on the codeplex site: http://sqliosimparser.codeplex.com/Thread/List.aspx -Jens...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/10/23/sqliosimparser-0-3-3-0-is-available.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9911983" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author></entry><entry><title>SQLIOSimParser 0.3.1.0 is available</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/10/17/sqliosimparser-0-3-1-0-is-available.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/10/17/sqliosimparser-0-3-1-0-is-available.aspx</id><published>2009-10-17T16:45:25Z</published><updated>2009-10-17T16:45:25Z</updated><content type="html">&amp;#160; These are the new functionalities comparing the 0.2.3.1 version: -Added n-m mapping for different test iterations (Suggestion to Jimmy) -Included output to CSV (Suggestion to Jimmy) -Being able to specify a delimiter for the CSV output (Suggestion to Jens) -Added an additional text column for using as TestName (Suggestion by Jimmy) -Changed column headings to include the units in most attributes (Suggestion by Jimmy and checked by Franz) Feedback is warmly welcome, either through the codeplex...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/10/17/sqliosimparser-0-3-1-0-is-available.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9908580" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author></entry><entry><title>SQL Server Reporting Services Logging &amp; Caching project released on Codeplex</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/10/12/sql-server-reporting-services-logging-caching-project-released-on-codeplex.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/10/12/sql-server-reporting-services-logging-caching-project-released-on-codeplex.aspx</id><published>2009-10-12T11:36:52Z</published><updated>2009-10-12T11:36:52Z</updated><content type="html">&amp;#160; The first version (0.3.0.0) of a small project I did was published to Codeplex ( http://rsparamlogcache.codeplex.com/ ). It enables you to log and cache user parameter values for further usage and statistics. Here is short extract from the project description: Project Description The solution tracks the selected parameters from a report execution and uses them later for the next execution to take them as default parameters. This enables users to log parameters and inspect the execution statistics...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/10/12/sql-server-reporting-services-logging-caching-project-released-on-codeplex.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9906083" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx" /><category term="Reporting Services" scheme="http://blogs.msdn.com/jenss/archive/tags/Reporting+Services/default.aspx" /></entry><entry><title>Jump on the Express Trace if you can – SQL Server Express server side tracing</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/10/03/jump-on-the-express-trace-if-you-can-sql-server-express-server-side-tracing.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/10/03/jump-on-the-express-trace-if-you-can-sql-server-express-server-side-tracing.aspx</id><published>2009-10-03T19:25:00Z</published><updated>2009-10-03T19:25:00Z</updated><content type="html">Running SQL Server Traces on SQL Server Express SQL Server Express does not come with a SQL Server Profiler GUI. (Period) Though can still use SQL Server Profiler tools from other editions to connect to the SQL Server Express edition. (But make sure that you do have a valid license for that.) (I appreciate all the work done by many community members developing a SQL Server Profiler Trace tool for SQL Server Express which can be found here. But in some cases you cannot use any external tools due to...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/10/03/jump-on-the-express-trace-if-you-can-sql-server-express-server-side-tracing.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9902773" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author></entry><entry><title>New Cumulative Update for CU4 for SQL Server 2008 SP1</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/10/03/new-cumulative-update-for-cu4-for-sql-server-2008-sp1.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/10/03/new-cumulative-update-for-cu4-for-sql-server-2008-sp1.aspx</id><published>2009-10-03T19:08:18Z</published><updated>2009-10-03T19:08:18Z</updated><content type="html">&amp;#160; Head up, the new CU is ready ! This one is CU (Cumulative Update) 4 for SQL Server 2008 SP1 (means that you will need to have SP1 installed in order to install the update) See the information of the release services team here: http://blogs.msdn.com/sqlreleaseservices/archive/2009/09/22/cumulative-update-4-for-sql-server-2008-sp1.aspx -Jens...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/10/03/new-cumulative-update-for-cu4-for-sql-server-2008-sp1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9902772" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author></entry><entry><title>Project corruption after upgrade VSTSDB &amp; Unit tests</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/10/03/project-corruption-after-upgrade-vstsdb-unit-tests.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/10/03/project-corruption-after-upgrade-vstsdb-unit-tests.aspx</id><published>2009-10-03T18:33:33Z</published><updated>2009-10-03T18:33:33Z</updated><content type="html">As it was hard to find the cause of this error and the answer, I wanted to share some searchable information on the internet for that. The following problem occurs while doing an upgrade of “older” VSDB project to the new GDR releases. As you have seen, the version of some assemblies within the GDR changed from 9.0.0.0 to 9.1.0.0. During a project upgrade you find yourself in one of the following errors: &amp;#160; &amp;#160; (For search sake the error reads “Cannot add a ConfigurationSection with the same...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/10/03/project-corruption-after-upgrade-vstsdb-unit-tests.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9902769" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author></entry><entry><title>Basta Herbst 2009 in Mainz</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/09/30/basta-herbst-2009-in-mainz.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/09/30/basta-herbst-2009-in-mainz.aspx</id><published>2009-09-30T23:49:07Z</published><updated>2009-09-30T23:49:07Z</updated><content type="html">Thank for all participants attending my sessions in Mainz. As promised, here are the slide decks and demos I used during my presentations. If you have any question to this are other SQL Server related topics, feel free to ping me. I am looking forward to hear from you ! Volltext voraus – Volltextindizierung in SQL Server Database lifecycle mit Visual Studio Team Database Edition -Jens...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/09/30/basta-herbst-2009-in-mainz.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9901494" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author></entry><entry><title>SQLDays in Rosenheim Herbst 2009</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/09/30/sqldays-in-rosenheim-herbst-2009.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/09/30/sqldays-in-rosenheim-herbst-2009.aspx</id><published>2009-09-30T21:59:47Z</published><updated>2009-09-30T21:59:47Z</updated><content type="html">&amp;#160; Thank for all participants attending my sessions in Mainz. As promised, here are the slide decks and demos I used during my presentations. If you have any question to this are other SQL Server related topics, feel free to ping me. I am looking forward to hear from you ! Volltext voraus – Volltextindizierung in SQL Server Implement now – performance later BTW, I didn’t forget the question I put in my backlog. If a table is partitioned and I have fulltext-indexed the table, will be switch off...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/09/30/sqldays-in-rosenheim-herbst-2009.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9901455" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author></entry><entry><title>Need more spare time ? Use SQLIOSimParser to interpret your IO results !</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/09/27/need-more-spare-time-use-sqliosimparser-to-interpret-your-io-results.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/09/27/need-more-spare-time-use-sqliosimparser-to-interpret-your-io-results.aspx</id><published>2009-09-27T19:14:45Z</published><updated>2009-09-27T19:14:45Z</updated><content type="html">&amp;#160; My colleague Marvelous Jimmy ( JimmyMay ) and myself did a small project to parse and interpret the results of the testing tool SQLIO. It produces ready-to-interpret reports and reusable results in Excel and will save you (as of Jimmy) much time doing your performance tracing and giving your more spare time to to fun stuff like… more Performance tracing sessions :-) Check out his blog post about the functionality and the walkthrough with a small sample. -Jens...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/09/27/need-more-spare-time-use-sqliosimparser-to-interpret-your-io-results.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9900011" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx" /><category term=".Net" scheme="http://blogs.msdn.com/jenss/archive/tags/.Net/default.aspx" /><category term="ADO.NET" scheme="http://blogs.msdn.com/jenss/archive/tags/ADO.NET/default.aspx" /><category term="SQLIOSimParser" scheme="http://blogs.msdn.com/jenss/archive/tags/SQLIOSimParser/default.aspx" /></entry><entry><title>Problems opening your project files in Visual Studio ?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/09/25/problems-opening-your-project-files-in-visual-studio.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/09/25/problems-opening-your-project-files-in-visual-studio.aspx</id><published>2009-09-25T11:59:20Z</published><updated>2009-09-25T11:59:20Z</updated><content type="html">&amp;#160; if you encounter the problem as follows: &amp;lt;PathToyourDBFile&amp;gt; cannot be opened because its project type (.dbproj) is not supported by this version of the application. To open it, please use a version that supports this type of project. ..then you might have a problem with the registration of your dbproj extension (Team database edition projects). If a restart does not fix the problem, you can use the following command to start Visual Studio: Open the Visual Studio Command prompt Launch...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/09/25/problems-opening-your-project-files-in-visual-studio.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9899404" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author><category term="Visual Studio for Database Professionals" scheme="http://blogs.msdn.com/jenss/archive/tags/Visual+Studio+for+Database+Professionals/default.aspx" /><category term="Data Dude" scheme="http://blogs.msdn.com/jenss/archive/tags/Data+Dude/default.aspx" /></entry><entry><title>Cannot find the source of a SQL Server error ?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/09/25/cannot-find-the-source-of-a-sql-server-error.aspx" /><id>http://blogs.msdn.com/jenss/archive/2009/09/25/cannot-find-the-source-of-a-sql-server-error.aspx</id><published>2009-09-25T11:33:24Z</published><updated>2009-09-25T11:33:24Z</updated><content type="html">Ever had an error in your application and you couldn't find the source of all evil and where the error is thrown at the end ? Well, SQL Server profiler does a great job about that, but you really need to understand which events to filter for and how to correlate the results in order to know where to dig into. (I was inspired for this blog entry by Dirk van Coeverden , a colleague within MS who threw up this question on our internal alias list) The sample I use using is straightforward and basically...(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/09/25/cannot-find-the-source-of-a-sql-server-error.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9899392" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx" /><category term="T-SQL" scheme="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx" /><category term="Profiler" scheme="http://blogs.msdn.com/jenss/archive/tags/Profiler/default.aspx" /></entry><entry><title>(Log) resistance is futile – how to drop log files</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jenss/archive/2009/09/18/log-resistance-is-futile-how-to-drop-log-files.aspx" /><link rel="enclosure" type="application/octet-stream" length="2883" href="http://blogs.msdn.com/jenss/attachment/9896976.ashx" /><id>http://blogs.msdn.com/jenss/archive/2009/09/18/log-resistance-is-futile-how-to-drop-log-files.aspx</id><published>2009-09-19T00:22:00Z</published><updated>2009-09-19T00:22:00Z</updated><content type="html">At the beginning everyone is trying to tune the database by creating additional database files, spreading the data across file groups, adding additional log files for the database… But wait a minute, is there a performance benefit from having more than one log file in the database ? Not really. This is due to the fact that SQL Server writes synchronously and serially to the log(s) and only uses one log file at a time. So better than having more than log file is to have the one you have sized appropriately....(&lt;a href="http://blogs.msdn.com/jenss/archive/2009/09/18/log-resistance-is-futile-how-to-drop-log-files.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9896976" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/members/JensS.aspx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2000/default.aspx" /><category term="SQL Server" scheme="http://blogs.msdn.com/jenss/archive/tags/SQL+Server/default.aspx" /></entry></feed>