In a nutshell, the three main steps involved in moving a database file to new location are: Set database to single user mode. Detach the database. Move database file to new location. Reattach the database by referencing the new location of the database file. Set database to multiple user mode. Note: There are 2 ways to... » read more
Copy–only backups are independent backup files that do not disrupt the regular Log Sequence Number (LSN) routine. This means that backup chains and restore sequences won’t be affected by the copy–only backup. A copy-only backup is a SQL Server backup that is independent of the sequence of conventional SQL Server backups. Usually, taking a backup changes the database and affects how later backups... » read more
At a minimum, every SQL Server database has two operating system files: a data file and a log file. Data files contain data and objects such as tables, indexes, stored procedures, and views. Log files contain the information that is required to recover all transactions in the database. Data files can be grouped together in... » read more
Highly recommend that you store all user databases, user database logs, and backups on a drive separate from the system drive. So in other words, if your SQL Server is installed on the C drive of a computer, you should be putting all of your data files on a separate drive, and the reason being... » read more
By default the database engine uses what’s known as an auto commit. Every T-SQL statement is committed or rolled back when it completes. The database engine will always use this auto commit functionality unless a transaction is explicitly specified with BEGIN TRAN. Implicit transaction are rarely used in SQL server and when the option is... » read more
Similar to Read Committed Isolation level but you can still read the old version of the data. Before a row is locked in preparation for changes, that means an update statement that might be run to a given row, that row is then placed in a version store (TempDB). The big advantage that our SCI... » read more
Low isolation levels do allow for more users to be able to access the data so you can get greater concurrency, but they can also affect data integrity by creating the effect of lost updates and dirty reads.Dirty reads are a phenomenon where you read uncommitted data. That data could be wrong, because its transaction... » read more
Table of Differences char nchar varchar nvarchar Character Data Type ASCII Unicode ASCII Unicode Maximum Length up to 8,000 characters up to 4,000 characters up to 8,000 characters up to 4,000 characters Character Size takes up 1 byte per character takes up 2 bytes per Unicode/Non-Unicode character takes up 1 byte per character takes... » read more
Nvarchar stores UNICODE data. If you have requirements to store UNICODE or multilingual data, nvarchar is the choice. Varchar stores ASCII data and should be your data type of choice for normal use. Regarding memory usage, nvarchar uses 2 bytes per character, whereas varchar uses 1. VARCHAR is stored as regular 8-bit data. But NVARCHAR strings are stored in the database as UTF-16 — 16 bits... » read more
SQL Server gives us a limit of 900 bytes for clustering keys, and 1700 bytes for non-clustered indexes. Have to use full-text index for VARCHAR(MAX) or nVARCHAR(MAX) datatypes.