SQL Profiler bug

May 31, 2007 · 1 min read

I discovered the most fascinating and annoying bug in version 9.00.1399.06 (the RTM version) of SQL Profiler 2005 today.  When I would execute a stored procedure from ASP.Net, the date parameters shown in the Profiler window would always have two single quotes on both sides, e.g. ''2/2/2002 22:00:00'' (yes, those are single quotes, not double)

This of course returns an error if you copy the statement and try to run it in Query Analyzer.  I was baffled for hours.  How could this be happening?  And why does it seem like the stored procedures are executing fine?

I eventually realized that I wasn't using the latest version of Profiler, so I decided to download SP2 for SQL Server 2005.  I installed it and ran the procedures again, and voila!  Everything looks normal now, and I can sleep tonight.

This article is part of the GWB Archives. Original Author: Alex Bransky

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.