sql server - Does the location of a stored procedure affect its performance? -
i have large application contains "modules" such finance, hr, sales, customer service.
to make application manageable , distribute load, have decided give each module own database on single server. there going master database holding master information such information users, global lookup tables, , security stuff.
i trying decide whether place module-specific stored procedure in corresponding database, or whether keep them in master database. example there stored procedure named dbo.sales_customer_orders selects data sales database tables. , of course sp going executed lot of times users. therefore should in sales database or okay keep in master database in terms of performance/scalability/reliability/security.
does matter stored procedure resides in different database 1 selecting from?
in experience not experience immediate performance penalty sharding data across multiple databases , common practice in large n-tier applications. experience minor penalty upon moving databases different servers.
you see blog post several others on site talk correct way shard data importance of using multiple connection string's reads , writes facilitate scaling , possibly caching layer later on.
Comments
Post a Comment