locked
What are the scale out strategies that wouldn't include replication? RRS feed

  • Question

  • We are using a database that handles mission critical live information. We are experiencing performance problems and we are looking to scale out the database. We are not interested in replication strategies. Caching will be of no use as we are handling live information. So apart from these 2 I also read about DPV and DDR. Are there any other techniques that could be used to scale out our database? Please advice with some strategies. 

    mayooran99

    Monday, January 19, 2015 5:15 AM

Answers

  • Hi Mayooran99,

    According to your description, you want to find the scale out techniques except for DPV, DDR, and replication. Based on this article, SQL Server Service Broker could be your choice.

    Service Broker could be used to scale out processing and make processing itself asynchronous, rather than change the database or application data topology. The Service Broker infrastructure exists at the database level. In order to do any Service Broker processing, the Service Broker feature must be enabled in all databases where broker services are used. For more information about the process, please download and check this white paper.

    Regards,
    Michelle Li
    Tuesday, January 20, 2015 9:10 AM
  • Is there any reason why you are not interested in replication strategies? P2P is exactly there in SQL Server for this purpose, and I know places where this is used in large scale.

    Another option is to segregate reads and writes ( I dont know if you consider that scale out). If so you can use Always On.


    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

    Tuesday, January 20, 2015 9:35 AM

All replies

  • Hi

    Have you read this article?

    http://msdn.microsoft.com/en-us/library/aa479364.aspx


    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Monday, January 19, 2015 6:22 AM
  • Yes I have. And my question does say about the ones mentioned in that article. I cannot use those since  I cant use replication. Apart from DPV and DDR mentioned in there, are there any other strategies?

    mayooran99

    Monday, January 19, 2015 6:24 AM
  • Hi Mayooran99,

    According to your description, you want to find the scale out techniques except for DPV, DDR, and replication. Based on this article, SQL Server Service Broker could be your choice.

    Service Broker could be used to scale out processing and make processing itself asynchronous, rather than change the database or application data topology. The Service Broker infrastructure exists at the database level. In order to do any Service Broker processing, the Service Broker feature must be enabled in all databases where broker services are used. For more information about the process, please download and check this white paper.

    Regards,
    Michelle Li
    Tuesday, January 20, 2015 9:10 AM
  • Is there any reason why you are not interested in replication strategies? P2P is exactly there in SQL Server for this purpose, and I know places where this is used in large scale.

    Another option is to segregate reads and writes ( I dont know if you consider that scale out). If so you can use Always On.


    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

    Tuesday, January 20, 2015 9:35 AM