Archive
SQL Server – How to find Default data and log path for SQL Server 2012
To identify default data and log directories in SQL Server 2012 you can use SERVERPROPERTY() function. In SQL Server 2012 two new parameters are added to SERVERPROPERTY() function namely, InstanceDefaultDataPath and InstanceDefaultLogPath which returns the default data and log directories respectively.
It can be used as below:
SELECT [Default Data Path] = SERVERPROPERTY('InstanceDefaultDataPath')
SELECT [Default Log Path] = SERVERPROPERTY('InstanceDefaultLogPath')
GO
Result Set:
Default Data Path
C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012\MSSQL\DATA\
(1 row(s) affected)
Default Log Path
C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012\MSSQL\DATA\
(1 row(s) affected)
You can also get this information from Server Properties dialog box in SQL Server Management Studio.
To identify this information for earlier version of SQL Server you need to use xp_instance_regread extended stored procedure which returns data from registry.
Earlier I posted on identifying default data directory for multiple instances through registry which returns this information for all instances installed on server.
Hope This Helps!
Vishal
If you like this post, do like my Facebook Page -> SqlAndMe
EMail me your questions -> Vishal@SqlAndMe.com
Follow me on Twitter -> @SqlAndMe
SQL Server – Finding TCP Port Number SQL Instance is Listening on
By default SQL Server listens on TCP port number 1433, and for named instances TCP port is dynamically configured. There are several options available to get the listening port for SQL Server Instance.
Here are a few methods which we can use to get this information.
Method 1: SQL Server Configuration Manager
Method 2: Windows Event Viewer
Method 3: SQL Server Error Logs
Method 4: sys.dm_exec_connections DMV
Method 5: Reading registry using xp_instance_regread
Let's see how you can use each of these methods in detail:
Method 1: SQL Server Configuration Manager:
Step 1. Click Start > All Programs > Microsoft SQL Server 2012 > Configuration Tools > SQL Server Configuration Manager
Step 2. Go to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for <Instance Name>
Step 3. Right Click on TCP/IP and select Properties
Step 4. In TCP/IP Properties dialog box, go to IP Addresses tab and scroll down to IPAll group.
If SQL Server if configured to run on a static port it will be available in TCP Port textbox, and if it is configured on dynamic port then current port will be available in TCP Dynamic Ports textbox. Here my instance is listening on port number 61499.
Method 2: Windows Event Viewer:
When SQL Server is started it logs an event message as 'Server is listening on [ 'any' <ipv4> <port number>' in windows event logs. Here <port number> will be actual port number on which SQL Server is listening.
To view this using Event Viewer:
Step 1. Click Start > Administrative Tools > Event Viewer.
Note: If Administrative Tools are not available on Start menu, go to Start > Control Panel > System and Maintenance > Administrative Tools > View event logs
Step 2. Navigate to Event Viewer > Windows Logs > Application
Step 3. Since huge amount of event are logged, you need to use filtering to locate the required logs. Right click on Application and select Filter Current Log...
Step 4. You can filter the events by Event ID and Event source. The event we are interested in has Event ID of 26022, and it's source is SQL Server Instance. You need to filter by both Event ID and SQL Server Instance if you have multiple instances installed, for a single instance you can filter by Event ID only. Click on OK to apply the filter.
Step 5. Once the filter is applied, Locate message 'Server is listening on [ 'any' <ipv4> …'. As we can see from below screenshot that SQL Server Instance is running on TCP Port 61499.
Method 3: SQL Server Error Logs:
When SQL Server is started it also logs an message to SQL Server Error Logs. You can search for port number in SQL Server Error Logs by opening SQL Server Error Log in notepad or via T-SQL using extended stored procedure xp_ReadErrorLog as below:
EXEC xp_ReadErrorLog 0, 1, N'Server is listening on', N'any', NULL, NULL, 'DESC'
GO
Result Set:
LogDate ProcessInfo Text
2013-03-21 13:34:40.610 spid18s Server is listening on [ 'any' <ipv4> 61499].
2013-03-21 13:34:40.610 spid18s Server is listening on [ 'any' <ipv6> 61499].
(2 row(s) affected)
As we can see from the output that SQL Server Instance is listening on 61499.
Note: This method does not work if SQL Server Error Logs have been cycled. See sp_Cycle_ErrorLog for more information.
Method 4: sys.dm_exec_connections DMV:
DMVs return server state that can be used to monitor SQL Server Instance. We can use sys.dm_exec_connections DMV to identify the port number SQL Server Instance is listening on using below T-SQL code:
SELECT local_tcp_port
FROM sys.dm_exec_connections
WHERE session_id = @@SPID
GO
Result Set:
local_tcp_port
61499
(1 row(s) affected)
As we can see from the output… same as above ![]()
Method 5: Reading registry using xp_instance_regread:
Port number can also be retrieved from Windows Registry database.
We can use extended stored procedure xp_instance_regread to get port number information using below T-SQL code:
DECLARE @portNumber NVARCHAR(10)
EXEC xp_instance_regread
@rootkey = 'HKEY_LOCAL_MACHINE',
@key =
'Software\Microsoft\Microsoft SQL Server\MSSQLServer\SuperSocketNetLib\Tcp\IpAll',
@value_name = 'TcpDynamicPorts',
@value = @portNumber OUTPUT
SELECT [Port Number] = @portNumber
GO
Result Set:
Port Number
61499
(1 row(s) affected)
As we can see … same as above
![]()
Note: The above code will only work if SQL Server is configured to use dynamic port number. If SQL Server is configured on a static port, we need to use @value_name = 'TcpPort' as opposed to @value_name = 'TcpDynamicPorts'.
Hope This Helps!
Vishal
If you like this post, do like my Facebook Page -> SqlAndMe
EMail me your questions -> Vishal@SqlAndMe.com
Follow me on Twitter -> @SqlAndMe
SQL Server – How to check if you are running 32-bit or 64-bit version
There are two different command you can use to check if you are running 32-bit or 64-bit version of SQL Server.
Using @@VERSION:
You can user @@VERSION system variable to determine edition and architecture of SQL Server as below:
SELECT @@VERSION
Result Set:
Microsoft SQL Server 2012 (SP1) – 11.0.3000.0 (Intel X86)
Oct 19 2012 13:43:21
Copyright (c) Microsoft Corporation
Developer Edition on Windows NT 6.0 <X86> (Build 6002: Service Pack 2)
(1 row(s) affected)
This command returns both SQL Server and Operating system information. In the first line you get information about SQL Server, it's version and architecture. Here, x86 = 32-bit architecture and x64 = 64-bit architecture. Same it true for operating system.
Using SERVERPROPERTY():
We can also user SERVERPROPERTY() function to get information about SQL Server Edition and architecture.
SELECT SERVERPROPERTY('Edition')
Result Set:
Developer Edition
(1 row(s) affected)
From the output we can see that it's a Developer Edition instance and architecture is 32-bit. If it is 64-bit then '(64-bit)' will be appended to edition. i.e. For 64-bit the output will be 'Developer Edition (64-bit)'
Hope This Helps!
Vishal
If you like this post, do like my Facebook Page -> SqlAndMe
EMail me your questions -> Vishal@SqlAndMe.com
Follow me on Twitter -> @SqlAndMe
SQL Server – Changing Default Database Location for Server
When you create a new database in SQL Server without explicitly specifying database file locations, SQL Server created files in default location. This default location is configured when installing SQL Server.
If you need to change this default location once SQL Server is installed, you can change this in server properties.
Method 1: Change default database location via SQL Server Management Studio:
Step 1. Right Click on Server and Select "Properties".
Step 2. in the "Server Properties" dialog box, navigate to "Database Settings" tab and data/log files location under "Database default locations" group. You can also change default backup location here.
Step 3. Click on "OK" to apply changes.
All new databases will be created to new location unless specified explicitly.
Method 2: Change default database location using TSQL Code:
You can also change default database location using TSQL code, use below code to change data, log and backup location:
USE [master]
GO
– Change default location for data files
EXEC xp_instance_regwrite
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'DefaultData',
REG_SZ,
N'C:\MSSQL\Data'
GO
– Change default location for log files
EXEC xp_instance_regwrite
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'DefaultLog',
REG_SZ,
N'C:\MSSQL\Logs'
GO
– Change default location for backups
EXEC xp_instance_regwrite
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'BackupDirectory',
REG_SZ,
N'C:\MSSQL\Backups'
GO
Hope This Helps!
Vishal
If you like this post, do like my Facebook Page -> SqlAndMe
EMail me your questions -> Vishal@SqlAndMe.com
Follow me on Twitter -> @SqlAndMe
SQL Server – Start/Stop SQL Server from command line
You can start/stop SQL Server services using Services Console or SQL Server Configuration Manager. You can also perform these operation using command line in Windows. For this you must run command prompt with Administrative privileges.
Method 1: Start/Stop SQL Server using NET command:
You can start/stop SQL Server from command line using NET command as below:
NET Action Service Name or Service Display Name
Where Action can be Start or Stop, and you can either specify Service Name or Service Display Name. Service Name is actual name which is registered as service and Service Display Name is a Descriptive Name for Service. For example, for default instance of SQL Server Service Name is "MSSQLSERVER", and Service Display Name is "SQL Server (MSSQLSERVER)". Below is a screenshot of Service Properties to explain this:
To START SQL Server Service, use:
NET start MSSQLSERVER
OR
NET start "SQL Server (MSSQLSERVER)"
To STOP SQL Server Service, use:
NET stop MSSQLSERVER
OR
NET stop "SQL Server (MSSQLSERVER)"
Method 2: Start/Stop SQL Server using SC command line utility:
The main advantage of using SC utility to start services is you can specify startup parameters while starting a service:
You can start/stop SQL Server from command line using SC utility as below:
SC Action Service Name or Service Display Name [Optional Parameters]
To START SQL Server Service, use:
SC start MSSQLSERVER
OR
SC start "SQL Server (MSSQLSERVER)"
To START SQL Server Service with parameters, use:
SC start MSSQLSERVER -m
OR
SC start "SQL Server (MSSQLSERVER)" -m
* The -m switch starts SQL Server in single user mode.
To STOP SQL Server Service, use:
SC stop MSSQLSERVER
OR
SC stop "SQL Server (MSSQLSERVER)"
Hope This Helps!
Vishal
If you like this post, do like my Facebook Page -> SqlAndMe
EMail me your questions -> Vishal@SqlAndMe.com
Follow me on Twitter -> @SqlAndMe
SQL Server – Check Enabled Trace Flags for Server
In SQL Server you can enable a Trace Flag at session (effective for current session only) level and global level. If you are not sure which Trace Flags have been enabled you can use DBCC TRACESTATUS() command to get a list of enabled Trace Flags.
DBCC TRACESTATUS() takes two arguments <Trace Flag Number> and <Trace Scope>.
It can be used in following different ways.
To display Trace Flags which are enabled in current session + globally enabled Trace Flags
DBCC TRACESTATUS(-1)
GO
DBCC TRACESTATUS()
GO
To display status of individual Trace Flags which are enabled.
DBCC TRACESTATUS(3023, 3604)
GO
The output of DBCC TRACESTATUS() is as below:
This status of Trace Flags can also be obtained from SQL Server error logs. Although it required more effort you can use xp_ReadErrorLog to get this information from error logs using below T-SQL:
EXEC xp_ReadErrorLog 0, 1, 'DBCC TRACE'
GO
You can find more information on xp_ReadErrorLog here.
Hope This Helps!
Vishal
If you like this post, do like my Facebook Page -> SqlAndMe
EMail me your questions -> Vishal@SqlAndMe.com
Follow me on Twitter -> @SqlAndMe
SQL Server – Enabling backup CHECKSUM with Trace Flag 3023
You can use WITH CHECKSUM option to perform checksum when backup is created. When used this verifies each page for checksum and torn page.
You can use it in a BACKUP command as below:
BACKUP DATABASE [SqlAndMe]
TO DISK = N'C:\SqlAndMe.bak'
WITH CHECKSUM
GO
Once the backup is created you can check the header to verify if backup was created with checksum.
RESTORE HEADERONLY
FROM DISK = N'C:\SqlAndMe.bak'
GO
Result Set:
However, if you do not have control over underlying T-SQL for backup then you can enable backup checksums using Trace Flag 3023. When this Trace Flag is turned on WITH CHECKSUM option is applied automatically for a backup.
In the following example I have run a backup before enabling Trace Flag 3023, and after enabling Trace Flag 3023 to see it’s behavior:
– Run without Trace Flag 3023
BACKUP DATABASE [SqlAndMe]
TO DISK = N'C:\SqlAndMe.bak'
GO
DBCC TRACEON(3023)
GO
– Run after enabling Trace Flag 3023
BACKUP DATABASE [SqlAndMe]
TO DISK = N'C:\SqlAndMe.bak'
GO
DBCC TRACEOFF(3023)
GO
Result Set:
Processed 240 pages for database 'SqlAndMe', file 'SqlAndMe' on file 1.
Processed 1 pages for database 'SqlAndMe', file 'SqlAndMe_Log' on file 1.
BACKUP DATABASE successfully processed 241 pages in 0.213 seconds (8.839 MB/sec).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Processed 240 pages for database 'SqlAndMe', file 'SqlAndMe' on file 2.
Processed 1 pages for database 'SqlAndMe', file 'SqlAndMe_Log' on file 2.
BACKUP DATABASE successfully processed 241 pages in 0.376 seconds (5.007 MB/sec).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Now, we can look at the header of the backup file to verify if the backup has been created with checksum:
RESTORE HEADERONLY
FROM DISK = N'C:\SqlAndMe.bak'
GO
Result Set:
As we can see from the output, First backup was created without checksums and second backup (after enabling Trace Flag 3023) is created with checksums without explicitly specifying WITH CHECKSUM option.
Hope This Helps!
Vishal
If you like this post, do like my Facebook Page -> SqlAndMe
EMail me your questions -> Vishal@SqlAndMe.com
Follow me on Twitter -> @SqlAndMe
SQL Server – Login Failed, cannot open user default database
Each login in SQL Server has a default database associated with it. When you login to SQL Server context is set to default database for login. This is set when login is created and it can be changed by using ALTER LOGIN command.
If for some reason the default database is not available on server you cannot login to SQL Server, an error message is received as below:
To resolve this error you need to change the default database which the login account uses. You can do this by logging in using a system administrator account or a different account which has securityadmin privileges.
Solution 1:
In case you do not have access to a system admin account, you can change the database which is used after logging via "Connect to Server" window in SQL Server Management Studio.
1. Provide "Server name", "Login" and "Password" information:
2. Click on "Options >>>" to open "Connection Properties" tab:
3. Provide a different database name (preferably 'master') manually for "Connect to database" replacing <default>. (<Browse Server…> will not work here), and click on "Connect".
Now you should be able to login successfully. However, this solution does not address the problem permanently. You will be need to do the same exercise if you are logging in from a different machine. (It will work on same machine due to the face that SQL Server Management Studio remembers your choice..)
Solution 2:
In order to fix the issue permanently you need to change the default database for login. You can do this using SQL Server Management Studio or T-SQL. You will need an account with sysadmin or securityadmin privileges.
1. Login to SQL Server using account with appropriate privileges.
2. Locate Login with issues under Server > Security > Logins in Object Explorer.
3. Right click on Login and select "Properties" from the context-menu.
4. In the "Login Properties" window change the default database by selecting a default database and click on "OK" to apply changes:
That’s all, now you should be able to login to SQL Server without any issues.
If you are a T-SQL fan you can also change the default database for login using ALTER LOGIN command as below:
USE [master]
GO
ALTER LOGIN [Vishal]
WITH DEFAULT_DATABASE = [SqlAndMe]
GO
Results:
Command(s) completed successfully.
Hope This Helps!
Vishal
If you like this post, do like my Facebook Page -> SqlAndMe
EMail me your questions -> Vishal@SqlAndMe.com
Follow me on Twitter -> @SqlAndMe

