locked
Server in DB Issue RRS feed

  • Question

  • Hello Team,

    I have two servers(S1 and S2) AND 5 Databases(D1,D2,D3,D4,D5) and in server S1 have 3 database(D1,D2,D3) and in server S2 have 2 database(D4,D5)
    and  need to reduce the cost of the server.How has to be done.

    Thanks in advance

    RK

    Friday, May 29, 2020 6:50 AM

All replies

  • Are they separate SQL DBs or part of elastic pools? 

    Please check this to know elastic pools concept - https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overview

    Also you will have to scale up, down the db config to save cost. See below as well - 
    Pricing Calculator | Microsoft Azure


    If the response helped, do "Mark as answer" and upvote it
    - Vaibhav

    Friday, May 29, 2020 1:43 PM
  • When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server). This error is returned by the instance of the Database Engine that hosts the report server database. In most cases, this error occurs because the SQL Server service is stopped. Or, if you are using SQL Server Express with Advanced Services or a named instance, this error will occur if the report server URL or connection string for the report server database is not correct. To work through these issues, do the following:

    Verify that the SQL Server (MSSQLSERVER) service is started. On the computer that hosts the instance of the Database Engine, click Start, click Administrative Tools, click Services, and scroll to SQL Server (MSSQLSERVER). If it is not started, right-click the service, select Properties, in Startup Type select Automatic, click Apply, click Start, and then click OK.
    Verify that the report server URL and report server database connection string is correct. If Reporting Services or the Database Engine was installed as a named instance, the default connection string that is created during Setup will include the instance name. For example, if you installed a default instance of SQL Server Express with Advanced Services on a server named DEVSRV01, the web portal URL is DEVSRV01\Reports$SQLEXPRESS. Furthermore, the database server name in the connection string will resemble DEVSRV01\SQLEXPRESS. For more information about URLs and data source connection strings for SQL Server Express, see Reporting Services in SQL Server Express with Advanced Services. To verify the connection string for the report server database, start the Reporting Services Configuration tool and view the Database Setup page.
    Friday, May 29, 2020 2:46 PM
  • There are two ways forward -

    1. If your databases have unpredictable usage patterns, you can plan to move your databases inside an elastic pool. For example - if you have all your databases with 100 DTUs each, having an elastic pool with ~300 DTUs might be a better option for you than having 5*100 DTUs. Think of elastic pool as a pool of resources that can be shared across different databases. This way, you can share costs between databases and eventually save some dollars. Please be aware that since the underlying resources are shared in elastic pool, if one of your databases consumes most of the resources, it might slow down or impact your other databases in the elastic pool. Check out how to choose the right elastic pool size - https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overview#how-do-i-choose-the-correct-pool-size

    2
    . If elastic pool is not something that works for you, review your database usage and scale them down if they have not been using the resources to the fullest. You might also consider moving to a different tier to save costs, if that fits your needs. Follow this link to scale up or down your databases - https://docs.microsoft.com/en-us/azure/azure-sql/database/scale-resources

    Hope it helps!


    - Vaibhav Gujral

    Friday, May 29, 2020 2:59 PM
  • seprate DBs
    Monday, June 1, 2020 5:20 AM
  • Hi Rohit

    As mentioned by our Community members, as you have separate DB's you can try creating the  Elastic pools so that resources are not wasted and fully utilized. 

    Please get back to us if you have any further questions.

    Thanks
    Navtej S

    Wednesday, June 3, 2020 1:34 AM
  • Hello All,

    I got the points Butt as mentioned in the main question as a mentioned in first server(S1) there are 3 dbs(DB1,DB2,DB3) and in Server(S2) there are 2 dbs(DB4,DB5) Whether can we combine 
    all the 5 dbs from 2 different servers and do the elastic pool for 5 dbs or need to do separate like S1 3 dbs one elastic pool and another S2 2 dbs another elastics pool Please advise.

    Regards

    RK

    Wednesday, June 3, 2020 8:10 AM
  • Hi Rohit

    You have really specific case and this will require extensive testing and POC creation on your part. If your DB's have different load at different times, elastic pool makes sense. If the DB load is high and constant on all DB's that doesnt make sense.

    Also Elastic pools has its limitations according to tier:
    https://docs.microsoft.com/en-us/azure/azure-sql/database/resource-limits-vcore-elastic-pools

    https://docs.microsoft.com/en-us/azure/azure-sql/database/resource-limits-dtu-elastic-pools

    If you end up choosing a Elastic pool of a higher tier because your load is such, You may end up paying more than what you pay now. 

    Please go ahead and create test scenarios to check how your DB's behave in a elastic pool or even merging them on one logical SQL server.

    Thanks

    Navtej S

    Wednesday, June 3, 2020 12:56 PM