• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

cfqueryparam and SQL 2005

New Here ,
Jun 08, 2006 Jun 08, 2006

Copy link to clipboard

Copied

I've heard a rumor, which I can't find any verification, that sql server 2005 makes cfqueryparam useless. Has anyone else heard of this and can point to a reference that spells this out? Or does anyone have categorical proof that cfqueryparam is still needed in sql server 2005?
TOPICS
Advanced techniques

Views

449

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 08, 2006 Jun 08, 2006

Copy link to clipboard

Copied

Useless?
Still needed?

Don't know about mssql, but with Oracle, cfqueryparam makes queries run faster. What is the reason you are currently using it with mssql?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 08, 2006 Jun 08, 2006

Copy link to clipboard

Copied

I always use it in my code, but word is passing around that it's not necessary in mssql 2005, that it somehow auto handles it and the binding, but i can't find anything to back this up perception, and would like to correct this mis-perception and have proof to back up that cfqueryparam is still needed.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Jun 08, 2006 Jun 08, 2006

Copy link to clipboard

Copied

LATEST
If somebody makes a preposterous new claim, the burden is on THEM to prove it.
Don't fall for the trick that you must disprove such malarky.

Nothing's changed with SQL server 2005. From performance, decoupling, security, and maintainabilty perspectives: stored procedures work best, cfqueryparam next best, and ad hoc queries will bite you sooner or later.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 08, 2006 Jun 08, 2006

Copy link to clipboard

Copied

Still needed? But it's not needed now. There is a difference between beneficial and need you realize.

If you actually have sql 2005, make up some queries that you know will take at least a couple of seconds to run, and run them with and without cfqueryparam. If you notice no performance improvement with cfqueryparam, the perception you are combatting might actually be accurate.

From my point of view, increased query speed is the only thing that justifies the extra complications that cfqueryparam entails.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation