I want some Moore

Blog about stuff and things and stuff. Mostly about SQL server and .Net
posts - 226, comments - 2295, trackbacks - 33

My Links



Hi! My name is 
Mladen Prajdić  I'm from Slovenia and I'm currently working as a .Net (C#) and SQL Server developer.

I also speak at local user group meetings and conferences like SQLBits and NT Conference
Welcome to my blog.
SQL Server MVP

My Books

SQL Server MVP Deep Dives 2
The Red Gate Guide to SQL Server Team based Development Free e-book

My Blog Feed via Email
Follow MladenPrajdic on Twitter

Users Online: who's online

Article Categories


Post Categories

Cool software

Other Blogs

Other stuff

SQL stuff

July 2008 Blog Posts

Number one advice to recruiters from an IT guy

I can't stress this enough: Never ever call me on my work phone as a form of the first contact!  Unless I know you and have given you permission to call me, don't. Send me an email instead. I don't have anything against recruiters, I think their jobs are very important in the greater scheme of things.   I also never give my work phone number away, and if I have to I give my mobile phone number to people. So it's beyond me how do recruiters think it's actually OK to call me at work. It shows disrespect to me and to the company...

posted @ Thursday, July 24, 2008 7:07 PM | Feedback (12) | Filed Under [ Misc Work Conditions ]

Immediate deadlock notifications without changing existing code

In my previous post about immediate deadlock notifications in SQL Server 2005 I've shown a way to use a try catch block to get the deadlock error. The con of this method, although it uses best practice for error handling in SQL Server 2005, is that you have to change existing code and it doesn't work for non stored procedure code. And that IS a pretty BIG con! As is customary in this blog there is a solution to this. :)   SQL Server 2005 Event notifications Event notifications are a special kind of database object that send information...

posted @ Friday, July 18, 2008 11:00 AM | Feedback (12) | Filed Under [ SQL Server ]

SQL Server 2005 bug when using LIKE searches

Here's a demo of a nice little bug in SQL Server 2005 when using LIKE comparisons for searching. What is so "nice" about it is that it only manifests itself if your search ends in number 9 followed by a wildcard when selecting only columns covered by a nonclustered index. I've been able to reproduce the error on different collations and servers. They were all SQL Server 2005 SP2+. SQL Server 2000 isn't affected by this. You can find the connect issue posted by my coworker here. Craig Freedman pointed me to this connect issue that is...

posted @ Monday, July 14, 2008 11:43 AM | Feedback (11) |

Powered by:
Powered By Subtext Powered By ASP.NET