Views are also an excellent way to enforce security -- you can exclude
certain columns from the base table(s) when creating a view, and set
permissions for retrieval of the view but not the base table(s), to ensure
sensitive data isn't compromised.
-----Original Message-----
From: Jim Nitterauer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 29, 2001 9:16 AM
To: CF-Community
Subject: RE: Stored procedures...when would you
Views enhance performance very dramatically by doing the following:
1. SQL Server manages views as if they were actual tables therefore the
results of the SQL Statement defining the view are instantly available.
2. The Database connection - i.e. ODBC or preferably OLEDB does not have to
translate a complex SQL statement, pass it off to the DB server and wait for
the DB server to act on it. This lowers the overhead on the Web server in
some cases quite significantly.
3. You can define indexes for views that enhance performance significantly.
We have seen dramatic improvements in performance by switching from ODBC to
OLEDB and by incorporating views. Dramatic translates to 10 to 20 fold
decrease in processing time.
Jim Nitterauer
http://www.creativedata.net
-----Original Message-----
From: Bob Silverberg [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 29, 2001 8:09 AM
To: CF-Community
Subject: RE: Stored procedures...when would you
Now I'm wading in a bit over my head, as I'm no DBA, but I don't see how
views would improve performance. A view is really just a predefined query
template - it looks like a table, but it's just a big SQL statement - so I
don't see how executing a select against a view would perform any
differently than executing the exact same SQL statement against the base
tables themselves.
The one way in which a view could help is if SQL in the view is optimal.
Perhaps a user writing the SQL from scratch would not write the "best" SQL.
If you have your expert create the views then you know that your
"non-expert" users won't be issuing bad join statements against the base
tables.
Bob
-----Original Message-----
From: Joe Sheble aka Wizaerd [mailto:[EMAIL PROTECTED]]
Sent: March 29, 2001 8:56 AM
To: CF-Community
Subject: RE: Stored procedures...when would you
Isn't in true that there are significant performance gains when using Views
instead of Tables? What are some of the limitations of Views? For
example, they're not updatable right....
At 08:50 AM 3/29/01 -0500, you wrote:
>While SP's are faster the majority of the time but not always, as was
>already stated, another factor is the RDBMS it's running against. I
believe
>Oracle isn't really optimized for SP performance, though there certainly
are
>benefits aside from speed to consider.
>
>~Simon
>
>Simon Horwith
>Macromedia Certified Instructor
>Certified ColdFusion Developer
>Fig Leaf Software
>1400 16th St NW, # 500
>Washington DC 20036
>202.797.6570 (direct line)
>www.figleaf.com
>
>
>
>-----Original Message-----
>From: Angel Stewart [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, March 28, 2001 11:17 PM
>To: CF-Community
>Subject: Stored procedures...when would you
>
>
>NOT want to use stored procedures to run queries etc. on a database?
>
>Wouldn't a stored procedure almost always run faster than one done through
>CF?
>
>-Gel
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
