dphillips (11/12/2008)
I agree totally. Having a DEV who is primarily a DEV but act as DBA is where I have seen problems. I have yet to see a DBA who aids in DEV (and in fact often does some DEV whether by SPs, SSIS, or data access code) to be a problem anywhere, unless it becomes so much so that they do more DEV than DBA.A DBA who does not get familiar with how the data both is and needs to be used, and assist to those ends, is not a great DBA.
From time to time, I pickup a light project that is on the Dev teams back burner, and has not real deadline, and code it. I try to work with one of the Developers though so that in the event of a problem with my code in production, there is another avenue of support, and I provide copious comments in my C# code in summary blocks that makes it self documenting in XML form, so they should be able to follow it anyway. Personally I like to sling code. I enjoy seeing the fruits of my labors take form as I work.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]