From SQL Server 2012 to 2016 version, when SQL Server instance is restarted, then table’s Identity value is jumped and the actual jumped value depends on identity column data type. If it is integer (int) data type, then jump value is 1000 and if big integer (bigint), then jump value is 10000.
Highlighted Points :
Microsoft declares it is a feature rather than a bug and in many scenarios it would be helpful.
- Microsoft states this is not a bug and does not intend to provide a fix it. It will not be corrected in Patch fixes or service packs.
- If too many tables contain identity column to your database and all contain existing values, then it is better to go for solution 2. Because it is a very simple solution and its scope is server wise.
- If you want to create a new database and you need auto generated number field, then you can use solution 1, that means use sequence value to a column instead of auto Identity value.
· Trace Flag: 272
Function: Disabling the identity cache. It prevents identity gap after restarting SQL Server instance, critical for columns with identity and tinyint and smallint data types.
- Using Sequence
- Register -t272
- Upgrade to Sql server 2017
First, we need to remove Identity column from tables. Then create a sequence without cache feature and insert number from that sequence.
The following is the code sample:
CREATE SEQUENCE Id_Sequence
START WITH 1
INCREMENT BY 1
insert into MyTestTable values(NEXT VALUE FOR Id_Sequence, ‘Mr.ravi’);
insert into MyTestTable values(NEXT VALUE FOR Id_Sequence, ‘Mr.suresh’);
I recently implemented an AWS site-to-site VPN for a customer to connect their on-premise network to their newly deployed AWS account.The requirement was network level connectivity from their on-pr…
Source: AWS Site-to-Site VPN and Transit Gateway
This article will help you understand the detail information of each component when we backup under System State:
· Active Directory DC Database file (ntds.dit)
· Boot and System protected files
· COM+ Class registration database
· Registry info
· SYSVOL folder and its files
· IIS metabase
· Cluster service info (on cluster node only)
The script that is discussed in this section opens the firewall ports for SQL Server.
To create the script, follow these steps:
- Start Notepad.
- Copy and paste the following code into Notepad:
netsh advfirewall firewall add rule name="Open Port 80" dir=in action=allow protocol=TCP localport=80
@echo ========= SQL Server Ports ===================
@echo Enabling SQLServer default instance port 1433
netsh advfirewall firewall add rule name="SQL Server" dir=in action=allow protocol=TCP localport=1433
@echo Enabling Dedicated Admin Connection port 1434
netsh advfirewall firewall add rule name="SQL Admin Connection" dir=in action=allow protocol=TCP localport=1434
@echo Enabling Conventional SQL Server Service Broker port 4022
netsh advfirewall firewall add rule name="SQL Service Broker" dir=in action=allow protocol=TCP localport=4022
@echo Enabling Transact SQL/RPC port 135
netsh advfirewall firewall add rule name="SQL Debugger/RPC" dir=in action=allow protocol=TCP localport=135
@echo ========= Analysis Services Ports ==============
@echo Enabling SSAS Default Instance port 2383
netsh advfirewall firewall add rule name="Analysis Services" dir=in action=allow protocol=TCP localport=2383
@echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382
@echo ========= Misc Applications ==============
@echo Enabling HTTP port 80
netsh advfirewall firewall add rule name="HTTP" dir=in action=allow protocol=TCP localport=80
@echo Enabling SSL port 443
netsh advfirewall firewall add rule name="SSL" dir=in action=allow protocol=TCP localport=443
@echo Enabling port for SQL Server Browser Service's 'Browse' Button
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=UDP localport=1434
@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh firewall set multicastbroadcastresponse ENABLE
- Save the file as a .txt file by using the following name: OpenSqlServerPort.txt
- Rename the OpenSqlServerPort.txt file to the following: OpenSqlServerPort.bat
Before you run the OpenSqlServerPort.bat script, you must copy the script to the computer that has the firewall and then run the script on that computer. To run the script, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, use the cd command to move to the folder in which you saved the OpenSqlServerPort.bat file.
- To run the OpenSqlServerPort.bat script, type OpenSqlServerPort.bat at the command prompt, and then press Enter.