Hello, I have 2 server machines and will be hosting an SQL database (ms sql server 2016). I’m wondering what would be the best option/approach for a fail-over setup. Server machine #1 will be the primary database and server machine #2 will be the backup. In the case when server machine #1 goes down, server machine #2 will takeover. When server machine #1 goes online, the database of server ...
Pretty much the title. I'm unable to create a zone redundant Azure SQL Server and App Service Plan in any region. Any help or advice would be appreciated. Here is the output of a test script I wrot...
Each will have its own SQL Server, and also its own windows service writing timestamped data regularly to the DB. This service already has its own simple switchover/failover algorithm. For the behaviour of the databases, once the primary server goes offline, the backup computer's service will take over to write data to the backup database.
Closed 14 years ago. Possible Duplicate: Thoughts on index creation for SQL Server for missing indexes T-SQL for finding Redundant Indexes I am using SQL Server 2008 and have a database with more than 150 tables that have duplicate indexes. I found some sql scripts which will list the duplicate indexes, but I'm not sure if I should trust them.
Is anyone aware of a T-SQL script that can detect redundant indexes across an entire database? An example of a redundant index in a table would be as follows: Index 1: 'ColumnA', 'ColumnB', 'Colum...
SELECT * FROM user, message WHERE message.user_id=user.id AND user.status=1 The problem is that all rows about a certain user in the result set contain redundant columns that repeat the same data about that user (those fields retrieved from user table), only fields from the message table contain non-redundant information. Something like this:
I have two dbs on the server. Db1 is in the backup list is a Standard tier, serverless with geo-redundant backup. Db2 that is not in the backup list is a Basic tier, serverless, with zone-redundant backup. I'm wondering if its either 1) the different tier or 2) the different backup schemes that is preventing me from using a db backup?
As an aside, such "redundant" indexes are typically a sign of someone running the tuning advisor and having it blindly create all indexes, or getting a "missing index" hint in a query and blindly creating that index. These mechanisms don't consider the costs of indexes, only their benefits for particular queries.
I want to get redundant records from the database. Is my query correct for this? select (fields) from DB group by name, city having count(*) > 1 If wrong please let me know how can I correct ...
