Piotr Rodak

if datepart(dw, getdate()) in (6, 7)
use pubs;

So.. this is it

My first blog post. As someone said somewhere, sharing information forces you to look at it from every side, ensure that it is really correct. I will do my best to make so.

This blog is going to be about... SQL Server :). I am database developer and from time to time I come across quite interesting problems, up with (brilliant Wink) ideas, have some observations that I would like to share. Some of them will not be revolutionary but I hope that some of them will allow you to look at questions you have from different angle, which is always helpful, I noticed.

My main areas of interest are performance, programming, some SSIS, some c# will perhaps find their way here as well. We'll see.

Published 23 October 2007 21:55 by Piotr Rodak

Comments

# re: So.. this is it@ 24 October 2007 11:20

Welcome to sqlblogcasts blog Smile

by Madhivanan

# re: So.. this is it@ 25 October 2007 23:28

Welcome to the blogosphere. I'm looking forward to your brilliant ideas.

I like the philosophy "sharing information forces you to look at it from every side, ensure that it is really correct. I will do my best to make so"

Many don't do the latter

by simonsabin

# re: So.. this is it@ 04 November 2007 20:56

yeah, though I bet the stinging feeling on your proffessional ego made by correcting comment won't let mistakes linger in the net too long :)

by Piotr Rodak

# re: So.. this is it@ 13 November 2007 14:34

I have a trigger that I use to do consistancy checks on the application data just entered. I can't give the application an error to display to the end user, so I send an e-mail with msdb.dbo.sp_send_dbmail. We are upgrading versions of the app software (the old one used SA and the new one uses NT authentication). Now the trigger won't work. I have narrowed it down to this stored procedure. With NT authentication I don't have rights to even see this procedure.  I have logged on as administrator to the network, then myself to the application.  When I enter a transaction that causes the error, it works as it should and I get an e-mail.  Where do we go to change the security on the MSDB data base to allow execution of all of the stored procedures.

Sure need some ideas. We've looked everywhere and cannot solve it.

Thanks, Ed

by Nettestad