SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Calling COM From T-SQL


Calling COM From T-SQL

Author
Message
Dinesh Asanka
Dinesh Asanka
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2648 Visits: 223
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/dasanka/callingcomfromtsql.asp






My Blog: http://dineshasanka.spaces.live.com/
TheMOTU
TheMOTU
Grasshopper
Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)

Group: General Forum Members
Points: 22 Visits: 77

Conceptually, databases are to store and retrieve data - that what they do best.

Having "ability" doesn't mean you have to use it. As a DBA and developer, I strongly discourage people to use applications inside SQL Server, or any other database... Because I generally don't trust such applications to properly manage system resources. Using COM from T-SQL will slow down your SQL Server (at best). In most cases it will crash it eventually - fact.

Instead of "smart assing" with T-SQL, you (and your installation) will be better off by having a dedicated server to run application(s) which connect to database server for data.


James Luetkehoelter
James Luetkehoelter
SSC-Addicted
SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)

Group: General Forum Members
Points: 433 Visits: 33

First off -- very well written article! While as a practice I agree with the above post that this generally isn't a good idea, there are instances where I've seen it used effectively as a stop-gap measure to re-writing an entire application.

It certainly is a security risk (many recommend removing the OA procedures althogether), and there is a visible performance depending on how often the COM object is instantiated.

With all the risks and performance hits, it is a handy feature to be aware of, but NEVER make it your primary plan of action. However, there are circumstances where it might be the only viable option. The realities of most companies place financial and temporal constraints on projects that cause us to consider options we would normally avoid at all costs.

Have I used the OA procedures in production work- no. Would I use them? Not on something I was building for a client. Would I tell a client that they absolutely should be removed if already used for an existing application? Not necessarily. I would point out the risks and costs involved, and stress to them that they should consider eliminating them in the future.

I think they are very useful to know about (and this was a well-written article introducing them), but should considered as a last resort or temporary work-around.





Dinesh Asanka
Dinesh Asanka
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2648 Visits: 223
yes it should be used as final "Trump", I should have mention these in the article. Sorry About it!!






My Blog: http://dineshasanka.spaces.live.com/
James Luetkehoelter
James Luetkehoelter
SSC-Addicted
SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)SSC-Addicted (433 reputation)

Group: General Forum Members
Points: 433 Visits: 33

Actually I like the article just as is. It's a great reference for someone in that "trump" situation. I didn't get the impression you advocating it's usage rather than exploring what it can do and how to use it. Sometimes I think it's good to separate information from recommended practice...

Again, Kudos. Well written an organized and will probably help somebody who has hit that "trump" situation





poornachander
poornachander
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 7
he he he ......Stop copying from MSDN

http://msdn.microsoft.com/en-us/library/aa238863(SQL.80).aspx
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search