Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SreenivasBora
Posting Yak Master
164 Posts |
 Posted - 2010-02-02 : 15:10:03
|
| Guy,Can any one help me, Any PERFORMANCE/SECURITY issues on SQL server side while using ASSEMBLY instead of Stored procedures?RegardsSREENI |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2010-02-04 : 05:34:43
|
| An assembly is a compiled .dll while a stored procedure might get recompiled numerous times during runtime so I guess the answer is that an assembly is by "default" faster. But as Tara says it all depends on the coding...if your .NET-coding sucks and your SQL coding rocks then the answer might be different.- LumbagoIf the facts don't fit the theory, change the facts. Albert Einstein |
 |
|
|
SreenivasBora
Posting Yak Master
164 Posts |
Posted - 2010-02-17 : 12:43:15
|
| Our functionality is very stright forward. Developer written .Net dll (Purpose is: DLL to do the Xml validation using XSD and then applying XSLT as these things can’t be easily written in T-SQL ) and placed it as an assembly on SQLServer, accessing this assembly from SSIS package / 3rd party applciations. In order to perform this, we need to change/enable the default settings of database (such as “SET TRUSTWORTHY ON”) and SQL Server configuration. (“Enable CLR engine”). Before doing the changes, I would like to know is there any IMPACTS / disadvantages to enable these features on PROD server(s)?OR thinking ... ask developer to look for better solution than this!!!Any help, most welcome.RegardsSREENIWith RegardsSR |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
CREATE ASSEMBLY