[dba-SQLServer] Difference between views and queries

Arthur,

More often than not? 

> From: dba-sqlserver-bounces at databaseadvisors.com 
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf 
> Of Arthur Fuller
> Sent: Friday, June 25, 2004 4:23 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: RE: [dba-SQLServer] Difference between views and queries
> 
> 
> 1. I haven't yet seen a case where dynamic SQL is necessary. All it
> takes to avoid it is one or more well-constructed sprocs, IMO.

> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com 
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf 
> Of Arthur Fuller
> Sent: Tuesday, June 29, 2004 8:19 PM
> To: dba-sqlserver at databaseadvisors.com
> Subject: RE: [dba-SQLServer] Difference between views and queries
> 
<snip>

> I think dynamic SQL is for the lazy. So there, I said it. 

You really would characterize your responses as that balanced? I find
your current restatement far more agreeable. Of course, I could add
similar comments about people who's databases aren't fully normalized.
Most of the time it is due to laziness and causes inefficiency and
requires greater coding. Yet, sometimes it is necessary. Would you
then make those same statements from above about everyone whose database
isn't fully normalized? I would think you would at least be curious as
to why it was done before making such blanket statements.

Francis R Harvey III
WB 303, (301)294-3952
harveyf1 at westat.com


> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com 
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf 
> Of Arthur Fuller
> Sent: Wednesday, June 30, 2004 10:57 AM
> To: dba-sqlserver at databaseadvisors.com
> Subject: RE: [dba-SQLServer] Difference between views and queries
> 
> 
> Good example, and good reasoning, and I agree that dynamic 
> SQL is never
> out of the question. What I intended to write is that more often than
> not, dynamic SQL is the lazy way out of thinking carefully 
> about sprocs.
> Most of the time it is unnecessary and costly in terms of performance
> and front-end code; some of the time, there is no other way.
> 
> Arthur
<snip>