grouping methods in a DLL, where is the break point?

Hot Topic

Using an External Dataset with Reporting Services
Notifications to Live Communication Server?
Making outbound HTTP requests from SQLCLR
3 Management Studio Bugs
Deploy packages to an MSDB subfolder
To add one report or many
Unable to load client print control
AutoClose
invalid object name 'sys.objects'
Why can I not read VARCHAR(MAX)?

SQL Server

Generation of a report in background or asynchronously.?
"SQL Everywhere" is a Sybase trademark
SQL Server Import Copy or Query
Convert numbers to Month Name
Linked Server Problem SQL Server 2005 to SQL Server 2000
SCD and populating dimensions and facts
query distribution using service broker
how to SQL server name and system name
Report Builder - is this a bug or is it by design?
connecting using "datasource=localhost"

grouping methods in a DLL, where is the break point?

We have roughly 5000 methods generated into C# that need to get assembled into DLLs and then put out as assmeblies in a SQL Server database. We then intend on creating user-defined functions to call many of these directly.

We can break these 5000 down into bundles and make about 10 DLLs, OR we can make 5000 DLLs. What are the concerns from a run-time perspective

If we go with 5000 DLLs, will an end user performing a few ad-hoc queries that use these user-defined functions experience poorer performance than if we had 10 large DLLs

Any input is appreciated. We'll be trying to assess the performance ourselves, but I'm looking for any stories about using large numbers of DLLs.

Thanks

Scott

Answer this question

grouping methods in a DLL, where is the break point?

  • Chaepp

    I'll let someone else comment on the possible performance implications, but I'd personally be more concerned with management.  5000 methods in a single DLL is definitely an issue because if you change one method you'll have to redeploy all of them.  Likewise with 5000 DLLs; I think you should try to group related methods in their own DLLs so that you can deploy and update them together.
     

    --
    Adam Machanic
    Pro SQL Server 2005, available now
    http://www..apress.com/book/bookDisplay.html bID=457
    --
     
     

    We have roughly 5000 methods generated into C# that need to get assembled into DLLs and then put out as assmeblies in a SQL Server database. We then intend on creating user-defined functions to call many of these directly.

    We can break these 5000 down into bundles and make about 10 DLLs, OR we can make 5000 DLLs. What are the concerns from a run-time perspective

    If we go with 5000 DLLs, will an end user performing a few ad-hoc queries that use these user-defined functions experience poorer performance than if we had 10 large DLLs

    Any input is appreciated. We'll be trying to assess the performance ourselves, but I'm looking for any stories about using large numbers of DLLs.

    Thanks

    Scott
  • grouping methods in a DLL, where is the break point?
Answer this question