<?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/b/jenss/atom.aspx</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/b/jenss/atom.aspx" /><generator uri="http://telligent.com" version="5.6.583.17018">Telligent Community 5.6.583.17018 (Build: 5.6.583.17018)</generator><updated>2009-09-27T17:14:45Z</updated><entry><title>Bulk Backup and Restore at the tip of your finger</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2011/09/08/bulk-backup-and-restore-at-the-tip-of-your-finger.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2011/09/08/bulk-backup-and-restore-at-the-tip-of-your-finger.aspx</id><published>2011-09-08T17:52:25Z</published><updated>2011-09-08T17:52:25Z</updated><content type="html">(Code can be downloaded here ) The Backup part “Can you please give me a recent backup of all user databases on that computer please ?” That is the sentence that will delay your planned work for the afternoon and will keep you busy for numerous hours depending on the number of databases you have in your environment. Wouldn´t it be nice to have something like an automated process that you can trigger to create those backups for you ? Well, that is what I thought some years ago and so I created a backup...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2011/09/08/bulk-backup-and-restore-at-the-tip-of-your-finger.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10208002" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="SQL Server" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server/" /><category term="T-SQL" scheme="http://blogs.msdn.com/b/jenss/archive/tags/T_2D00_SQL/" /><category term="T-SQL Procedure Logging" scheme="http://blogs.msdn.com/b/jenss/archive/tags/T_2D00_SQL+Procedure+Logging/" /><category term="T-SQL Procedure" scheme="http://blogs.msdn.com/b/jenss/archive/tags/T_2D00_SQL+Procedure/" /><category term="Administration" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Administration/" /><category term="testing" scheme="http://blogs.msdn.com/b/jenss/archive/tags/testing/" /><category term="DBA" scheme="http://blogs.msdn.com/b/jenss/archive/tags/DBA/" /></entry><entry><title>IsGuid or not isGuid, that is the question…</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2011/09/07/isguid-or-not-isguid-that-is-the-question.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2011/09/07/isguid-or-not-isguid-that-is-the-question.aspx</id><published>2011-09-07T19:04:00Z</published><updated>2011-09-07T19:04:00Z</updated><content type="html">As I was asked about a functionality how to check a string for being of the type GUID and only finding either solution with massive string operations, or using TRY..CATCH trying to CAST a value and then returning the CAST or CONVERT result, I created a new and simple one, based on a simple pattern matching using the LIKE operator: CREATE FUNCTION dbo.FnIsGuid ( &amp;#160;&amp;#160;&amp;#160; @StringToCheck NVARCHAR(36) ) RETURNS BIT AS BEGIN DECLARE @Result BIT = 0 SELECT @Result = 1 WHERE @StringToCheck LIKE...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2011/09/07/isguid-or-not-isguid-that-is-the-question.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10207160" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="T-SQL" scheme="http://blogs.msdn.com/b/jenss/archive/tags/T_2D00_SQL/" /></entry><entry><title>Get the NULL percentage of values in a specific table dynamically</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/08/28/get-the-null-percentage-of-values-in-a-specific-table-dynamically.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/08/28/get-the-null-percentage-of-values-in-a-specific-table-dynamically.aspx</id><published>2010-08-28T22:42:00Z</published><updated>2010-08-28T22:42:00Z</updated><content type="html">Nothing really fancy, but a small script I was now asked twice for. So I thought I publish it for the public and for the reference for others. It simply calculates the percentage of NULL values for a specific table in all columns. The last request was originated from the post here . 
 Be aware that this will scan the table entirely and might need some time for coming back. 
 You will get each column with an integer value as the percentage. This script will work on any version of SQL Server (except...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/08/28/get-the-null-percentage-of-values-in-a-specific-table-dynamically.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10055414" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="SQL Server" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server/" /><category term="T-SQL" scheme="http://blogs.msdn.com/b/jenss/archive/tags/T_2D00_SQL/" /><category term="SQL Server Agent" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+Agent/" /></entry><entry><title>ALM Visual Studio Database Projects Guidance is out in the wild !</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/08/21/alm-visual-studio-database-projects-guidance-is-out-in-the-wild.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/08/21/alm-visual-studio-database-projects-guidance-is-out-in-the-wild.aspx</id><published>2010-08-21T16:56:47Z</published><updated>2010-08-21T16:56:47Z</updated><content type="html">&amp;#160; After many months of hard work, collaboration, short weekends and nights, the new ALM Rangers guidance document is out covering Visual Studio Database Projects. Details about the documents and the documents themselves can be found here: Visual Studio Database Guide &amp;#160; on Codeplex &amp;#160; You will find a General guidance Specific scenarios HOLs for each topic Solution and Project Management Section Source Code Control and Configuration Management Integrating External Changes with the Project...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/08/21/alm-visual-studio-database-projects-guidance-is-out-in-the-wild.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10052776" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="Visual Studio for Database Professionals" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Visual+Studio+for+Database+Professionals/" /><category term="Data Dude" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Data+Dude/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="VSDBCMD" scheme="http://blogs.msdn.com/b/jenss/archive/tags/VSDBCMD/" /><category term="VSTSDB" scheme="http://blogs.msdn.com/b/jenss/archive/tags/VSTSDB/" /><category term="Guidance" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Guidance/" /><category term="Ranger" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Ranger/" /><category term="ALM" scheme="http://blogs.msdn.com/b/jenss/archive/tags/ALM/" /></entry><entry><title>Expand :r referenced files for SQLCMD into one file (SQLCmdScriptExpander)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/08/16/expand-r-referenced-files-for-sqlcmd-into-one-file-sqlcmdscriptexpander.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/08/16/expand-r-referenced-files-for-sqlcmd-into-one-file-sqlcmdscriptexpander.aspx</id><published>2010-08-16T17:47:42Z</published><updated>2010-08-16T17:47:42Z</updated><content type="html">Again a common question which I wanted to be able to answer once and for all: How can we expand files from a .sql file referenced with the :r operator ? Ok, lets make a step back in the past and see how we used to reference files in .sql files and calling them via OSQL or ISQL. The answer is, we couldn't. We needed to use either one file with the whole statement OR call OSQL/ISQL for each files separately. Now we have SQLCMD.EXE, the new command line utility for issuing SQL Server statements against...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/08/16/expand-r-referenced-files-for-sqlcmd-into-one-file-sqlcmdscriptexpander.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10050635" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server Deployment" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+Deployment/" /><category term="T-SQL" scheme="http://blogs.msdn.com/b/jenss/archive/tags/T_2D00_SQL/" /><category term="SCSE" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SCSE/" /><category term="SQLCmdScriptExpander" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQLCmdScriptExpander/" /><category term="SQLCMD" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQLCMD/" /></entry><entry><title>Script out jobs in SQL Server v2</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/08/13/script-out-jobs-in-sql-server-v2.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/08/13/script-out-jobs-in-sql-server-v2.aspx</id><published>2010-08-13T11:37:59Z</published><updated>2010-08-13T11:37:59Z</updated><content type="html">&amp;#160; For those asking a couple of times if the JobScripter for SQL Server Agent jobs is also available in 2008… here it is ! The only difference is that the version v2 is now targeting to SMO Assemblies of SQL Server 2008 which is version 10.0. This sure means that you are able to pick up the information from older servers as well. Only SQL Server 7.0 is not supported by this version of SMO. If you want to script out jobs from 7.0 you will need to use the old JobScripter version from the blog post...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/08/13/script-out-jobs-in-sql-server-v2.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10049791" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="SMO" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SMO/" /><category term="SQL Server Agent" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+Agent/" /></entry><entry><title>Database internal file versions– How to determine if the database was upgraded or created from scratch</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/07/28/database-internal-file-versions-how-to-determine-if-the-database-was-upgraded-or-created-from-scratch.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/07/28/database-internal-file-versions-how-to-determine-if-the-database-was-upgraded-or-created-from-scratch.aspx</id><published>2010-07-28T07:13:59Z</published><updated>2010-07-28T07:13:59Z</updated><content type="html">&amp;#160; In some cases it it interesting to know whether a database was directly created on the current version of the running SQL Server instance or if the database was upgraded during an upgrade of the instance or by attaching a database from an older version to a newer version of SQL Server. The information is stored in the datafile headers. To reveal it you will have to use the DBCC command and redirect the information to the trace output (by default this will be send to the errorlog) by using...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/07/28/database-internal-file-versions-how-to-determine-if-the-database-was-upgraded-or-created-from-scratch.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10043320" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="SQL Server" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server/" /><category term="T-SQL Procedure" scheme="http://blogs.msdn.com/b/jenss/archive/tags/T_2D00_SQL+Procedure/" /></entry><entry><title>Did your SQL Agent doze off and you don´t know which jobs to run afterwards ?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/07/23/did-your-sql-agent-doze-off-and-you-don-180-t-know-which-jobs-to-run-afterwards.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/07/23/did-your-sql-agent-doze-off-and-you-don-180-t-know-which-jobs-to-run-afterwards.aspx</id><published>2010-07-23T13:11:03Z</published><updated>2010-07-23T13:11:03Z</updated><content type="html">&amp;#160; In some cases you might face the problem that SQL Server Agent Service didn't come up or was stopped for reason. Jobs scheduled in the downtime will not run automatically when the Agent service comes up again, and that is a good thing. I often hear people saying, why isn’t that supposed to be the other way around? Shouldn’t the service revisit the schedules and see which ones he missed and run that ? The precise answer to that is – it depends. Imagine you have jobs doing Index maintenance...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/07/23/did-your-sql-agent-doze-off-and-you-don-180-t-know-which-jobs-to-run-afterwards.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10041843" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="SQL Server" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server/" /><category term="SQL Server Agent" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+Agent/" /></entry><entry><title>Database internal file versions–Where is the Undo button for a database upgrade ?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/07/19/database-internal-file-versions-where-is-the-undo-button-for-a-database-upgrade.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/07/19/database-internal-file-versions-where-is-the-undo-button-for-a-database-upgrade.aspx</id><published>2010-07-19T15:47:44Z</published><updated>2010-07-19T15:47:44Z</updated><content type="html">&amp;#160; A common question is how to move back to the older version of the database once upgraded. The answer is, you can´t . By attaching the database to the new SQL Server version an upgrade is done internally which can be seen if you run the attach commands in e.g. the script window of SSMS. In the following sample, I am attaching a SQL Server 2005 database to a SQL Server 2008 instance. The result is that it is upgraded during the attachment process (which also happens while restoring a backup...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/07/19/database-internal-file-versions-where-is-the-undo-button-for-a-database-upgrade.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10039874" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="SQL Server" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server/" /></entry><entry><title>SSIS as a data source for SSRS–where is it gone for SQL Server 2008 R2</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/07/11/ssis-as-a-data-source-for-ssrs-where-is-it-gone-for-sql-server-2008-r2.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/07/11/ssis-as-a-data-source-for-ssrs-where-is-it-gone-for-sql-server-2008-r2.aspx</id><published>2010-07-11T10:14:00Z</published><updated>2010-07-11T10:14:00Z</updated><content type="html">Some time ago I did a blog entry for SQL Server Integration Services packages as a data source for SQL Server Reporting Services reports. You can find this article here. This feature relies on a data processing extension that is explained in detail here ( http://msdn.microsoft.com/en-us/library/ms345250.aspx ). Due to security reasons, this feature has been deprecated and removed in SQL Server 2008 R2 . If you want to create and consume a more complicated data extraction you should think of either...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/07/11/ssis-as-a-data-source-for-ssrs-where-is-it-gone-for-sql-server-2008-r2.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10036860" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server Integration Services" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+Integration+Services/" /><category term="SSIS" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SSIS/" /><category term="SSRS" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SSRS/" /></entry><entry><title>Usage of @@Trancount in DML statements</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/07/10/usage-of-trancount-in-dml-statements.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/07/10/usage-of-trancount-in-dml-statements.aspx</id><published>2010-07-10T14:01:00Z</published><updated>2010-07-10T14:01:00Z</updated><content type="html">Some time ago I got an interesting questions why the following applies: 
 -- drop table a
 create table a(m varchar ( max ), i int )

 go 

 declare @cnt int 
--Explicit transaction 
 begin tran 
 set @cnt=@@trancount
insert into a select 'inside' , @@trancount 
insert into a select 'inside cnt' , @cnt
 commit tran 

 set @cnt=@@trancount

--Implicit transcation
insert into a select 'outside' , @@trancount 
insert into a select 'outside cnt' , @cnt 
 

 
 select * from a 
...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/07/10/usage-of-trancount-in-dml-statements.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10036731" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server/" /><category term="Transactions" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Transactions/" /></entry><entry><title>Light weight SQL Server procedure auditing without using SQL Server auditing version 2</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/07/10/light-weight-sql-server-procedure-auditing-without-using-sql-server-auditing-version-2.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/07/10/light-weight-sql-server-procedure-auditing-without-using-sql-server-auditing-version-2.aspx</id><published>2010-07-10T12:29:00Z</published><updated>2010-07-10T12:29:00Z</updated><content type="html">(The project is attached to this blog post, if you have any questions, feel free to send me a mail. You find the bits for download here .) 
 For all of you who haven&amp;acute;t been able to read my blog entry on logging yet, I suggest you to read the first version of the blog entry located here . It basically described the options for doing logging in your database and why I came up with this solution for you to share. To summarize the purpose of this logging solution, here are the basic steps: 
...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/07/10/light-weight-sql-server-procedure-auditing-without-using-sql-server-auditing-version-2.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10036720" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="Logging" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Logging/" /><category term="T-SQL Procedure Logging" scheme="http://blogs.msdn.com/b/jenss/archive/tags/T_2D00_SQL+Procedure+Logging/" /></entry><entry><title>The New! report in town</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2010/01/25/the-new-report-in-town.aspx" /><id>http://blogs.msdn.com/b/jenss/archive/2010/01/25/the-new-report-in-town.aspx</id><published>2010-01-25T06:19:38Z</published><updated>2010-01-25T06:19:38Z</updated><content type="html">Ever wondered what New! means if you see a report in SQL Server Reporting Services Manager ? Obviously it is a report which was created recently. But what does “recently” mean and do I have a way to influence what SQL Server identifies with “New!”. Well, sorry to say that, but it depends :-) The clear answer is: yes and no. There are two scenarios for this, the native mode and the SharePoint integrated one. For the Native mode you will see from the reflected sources that this setting is non-configurable...(&lt;a href="http://blogs.msdn.com/b/jenss/archive/2010/01/25/the-new-report-in-town.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9952785" width="1" height="1"&gt;</content><author><name>JensS</name><uri>http://blogs.msdn.com/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="Reporting Services" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Reporting+Services/" /></entry><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/b/jenss/archive/2009/11/18/want-to-know-what-happened-on-your-database-by-reading-the-transaction-log.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</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/b/jenss/archive/2009/11/06/an-secret-ssis-xml-destination-provider-you-might-not-found-yet.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="XML" scheme="http://blogs.msdn.com/b/jenss/archive/tags/XML/" /><category term="SSIS" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SSIS/" /></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/b/jenss/archive/2009/10/26/ssis-as-a-data-source-needed-watch-out-for-configuration-traps.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="XML" scheme="http://blogs.msdn.com/b/jenss/archive/tags/XML/" /><category term="SSIS" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SSIS/" /></entry><entry><title>SQLIOSIMParser 0.3.3.0 is available</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2009/10/23/sqliosimparser-0-3-3-0-is-available.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>SQLIOSimParser 0.3.1.0 is available</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2009/10/17/sqliosimparser-0-3-1-0-is-available.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</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/b/jenss/archive/2009/10/12/sql-server-reporting-services-logging-caching-project-released-on-codeplex.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term="Reporting Services" scheme="http://blogs.msdn.com/b/jenss/archive/tags/Reporting+Services/" /></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/b/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/b/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/b/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/JensS/ProfileUrlRedirect.ashx</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/b/jenss/archive/2009/10/03/new-cumulative-update-for-cu4-for-sql-server-2008-sp1.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</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/b/jenss/archive/2009/10/03/project-corruption-after-upgrade-vstsdb-unit-tests.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Basta Herbst 2009 in Mainz</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2009/09/30/basta-herbst-2009-in-mainz.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>SQLDays in Rosenheim Herbst 2009</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/jenss/archive/2009/09/30/sqldays-in-rosenheim-herbst-2009.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</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/b/jenss/archive/2009/09/27/need-more-spare-time-use-sqliosimparser-to-interpret-your-io-results.aspx" /><id>http://blogs.msdn.com/b/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/b/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/JensS/ProfileUrlRedirect.ashx</uri></author><category term="SQL Server 2008" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2008/" /><category term="SQL Server 2005" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2005/" /><category term="SQL Server 2000" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQL+Server+2000/" /><category term=".Net" scheme="http://blogs.msdn.com/b/jenss/archive/tags/-Net/" /><category term="ADO.NET" scheme="http://blogs.msdn.com/b/jenss/archive/tags/ADO-NET/" /><category term="SQLIOSimParser" scheme="http://blogs.msdn.com/b/jenss/archive/tags/SQLIOSimParser/" /></entry></feed>
