Re: Identity Column
- From: "Aaron Bertrand [SQL Server MVP]" <ten.xoc@xxxxxxxxxxxxxx>
- Date: Tue, 16 Jun 2009 13:10:54 -0400
Funny, I have never had a problem finding a stored procedure in a list.
Especially when proper error handling tells me which stored procedure
failed, and proper unit testing would have taken that mystery out of most
scenarios anyway.
So you're saying if I use stored procedures I can't refactor, or use source
control, or have code reviews? Hogwash. If these are your reasons for
avoiding stored procedures and dumping all of your ad hoc SQL in the data
layer, remind me to never work with you. Good luck.
You know why a DBA is always busy doing DBA stuff? Because they have
to find the stored procedures which broke the API from a list of 5000+
SPs (if it's legacy enough, all 5000 SPs should begin with "sp").
Ad hoc sql is not littered over countless applications, that's just a
poor argument (pure dba, see below). Ever heard of a data layer (the
physical tier)? You get full refactoring, source control, revision
control, super IDE, code review capability.
Again, this is not something a "pure" DBA who has never worked outside
of a SQL server would know.
.
- Follow-Ups:
- Re: Identity Column
- From: sqlguru
- Re: Identity Column
- References:
- Identity Column
- From: Sincere
- Re: Identity Column
- From: John Bell
- Re: Identity Column
- From: sqlguru
- Re: Identity Column
- From: Tony Rogerson
- Re: Identity Column
- From: sqlguru
- Re: Identity Column
- From: Tony Rogerson
- Re: Identity Column
- From: sqlguru
- Re: Identity Column
- From: Aaron Bertrand [SQL Server MVP]
- Re: Identity Column
- From: sqlguru
- Identity Column
- Prev by Date: Record Count in pagination table ROW_NUMBER() OVER
- Next by Date: Re: Record Count in pagination table ROW_NUMBER() OVER
- Previous by thread: Re: Identity Column
- Next by thread: Re: Identity Column
- Index(es):
Relevant Pages
|
