Tips for using SQL Server 2012 Transactional Replication SQL Server 2012 introduces AlwaysOn Availability Groups. This is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. AlwaysOn Availability Groups maximizes the availability of a set of user databases for an enterprise and supports a failover environment for a discrete set of user databases, known as availability...
Tag: performance
Tips for using SQL Server 2012 Snapshot Replication
Tips for using SQL Server 2012 Snapshot Replication SQL Server 2012 introduces AlwaysOn Availability Groups. This is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. AlwaysOn Availability Groups maximizes the availability of a set of user databases for an enterprise and supports a failover environment for a discrete set of user databases, known as availability...
Tips for using SQL Server 2012 stored procedures
Tips for using SQL Server 2012 stored procedures Include the SET NOCOUNT ON statement into your stored procedures. This can reduce network traffic, because your client will not receive the message indicating the number of rows affected by a Transact-SQL statement. Try to avoid using temporary tables and DDL (Data Definition Language) statements inside your stored procedure. Using temporary tables...
SQL Server 2012 Full-Text Search Optimization Tips
SQL Server 2012 Full-Text Search Optimization Tips Consider using the new custom NEAR option of the CONTAINS predicate or CONTAINSTABLE function. SQL Server 2012 introduces new custom NEAR option of the CONTAINS predicate or CONTAINSTABLE function. By using the custom NEAR option you can do the following: – optionally specify the maximum number of non-search terms that separate the first...
Tips for using SQL Server 2012 indexed views
Tips for using SQL Server 2012 indexed views One of the ways to optimize SQL Server 2012 performance is using indexed views. You can improve performance by creating a unique clustered index on the view, if the view is frequently referenced in queries that involve complex processing, such as aggregating lots of data or joining many rows. After creating a...
Tips for using SQL Server 2012 Distributed Queries
Tips for using SQL Server 2012 Distributed Queries Ensure that user own the table or a member of the sysadmin fixed server role, the db_owner fixed database role, or the db_ddladmin fixed database role on the linked server. To create the best query plans when you are using a table on a linked server that an instance of SQL Server,...
SQL Server 2012 XML Optimization Tips
SQL Server 2012 XML Optimization Tips Consider using the XML data type. This data type is used to store XML documents in table columns or Transact-SQL variables. The XML data type can be used in variables, columns, or in stored procedure and function parameters. You can build, rebuild or drop XML indexes online. In SQL Server 2012, indexes that include...
Tips for using SQL Server 2012 backup and restore
Tips for using SQL Server 2012 backup and restore Consider using page restores. SQL Server Management Studio supports page restores in SQL Server 2012. Now you can check database pages for corruption and restore selected corrupt pages from a database backup and subsequent log backups. Use the Database Recovery Advisor to construct restore plans that implement optimal correct restore sequences....
Tips for using SQL Server 2012 data types
Tips for using SQL Server 2012 data types Use tinyint data type, if you need to store integer data from 0 through 255. The columns with tinyint data type use only one byte to store their values, in comparison with two bytes, four bytes and eight bytes used to store smallint, int and bigint values accordingly. For example, if you...
Tips for using SQL Server 2012 constraints
Tips for using SQL Server 2012 constraints Try to create a single column constraint. The more columns the constraint will have, the slowly it will work and the more stored space it will require. Use cascading referential integrity constraints instead of triggers whenever possible. For example, if you need to make cascading deletes or updates, specify the ON DELETE or...