Bad DBA or Bad Developer?

I was browsing a public web site from a large company today, when I saw the error page shown below.  It looks like they are using ColdFusion to talk to SQL Server using JDBC, and they are missing a stored procedure called getBladeList.  This made me curious as to what might have happened.  I don’t know about Cold Fusion, but with ASP.NET, you can configure the web server to not expose such detailed error information to the end user, which is a good idea.

It also looks like the web site is hosted by a third party, rather than the actual large company.

 

image

Judging by the name of the SP and the purpose of the web site, this seems like a pretty important SP that was not just recently added by some rogue developer. Maybe the SP was accidentally dropped or renamed?  Maybe the code was changed to call a different stored procedure?

This entry was posted in SQL Server 2008 R2. Bookmark the permalink.

2 Responses to Bad DBA or Bad Developer?

  1. Yes, just like .NET, CF can be configured to not expose that information. It’s a setting in the CF Administrator, on the “debugging and logging” page. So in this case, it’s neither “bad dba” nor “bad dev” but “bad cf administrator” (or “bad hoster”).

    Of course, in many shops, they don’t have anyone really dedicated to the job, since generally there’s not much to do (except when things go wrong). We might then say “bad dev” then as often the CF Admin role falls to a developer (or the developers) doing most of the CF coding (as can happen in a .NET shop as well, of course).

    Thanks for all the great stuff in your blog, Glenn.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s