Skip to main content

Using GUID or UniqueIdentifiers in SQL Server

In order to differentiate between two rows, we normally use primary keys or identity values which may be same across two tables. In order to overcome this problem we can use a special type named "GUID". Its a hexadecimal number (Base 16) and the advantage is 
that they are unique across all databases and tables. 

 In SQL Server the same concept is implemented through UNIQUEIDENTIFIER data type. In order to generate a new value, we use the NEWID() function.

 For e.g. 

a. Creating a table that uses the UNIQUEIDENTIFIER datatype

 Create table Test
(
Empno uniqueidentifier,
Ename varchar(20)
)

b. Inserting rows in the tables with the use of NEWID() function
insert into Test values (newId(),'ABC')
insert into Test values (newid(),'XYZ')

insert into test values (newid(),'MNO')

 c. Selecting the rows from the table.

 Select * from test 

 Empno                                                                     Ename
6B2CF0E5-DC2E-4EB5-A090-71AD6C0EE260 ABC
917470F4-C165-4F21-8894-942C91E56BA9         XYZ
C7F3E70E-9972-45C6-A847-B4489F4B05FC MNO

 So we can see that the first column i.e. Empno is containing values that are unique and they are of type UniqueIdentifier. Its another way of having primary key in the table.

Comments

Post a Comment

Popular posts from this blog

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.
1 comment
Read more

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc . In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations. 1. Installation of required packages In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation: i. npm install knex ii. npm install mssql Once the packages are installed, we can write the following code to connect: //Code to KNEX connection settings. var knex = require('knex')({ client: 'mssql', connection: { user: 'sa', password: 'pwd', server: 'localhost', database: 'Test' } }); //Code to query the Table DEPT knex.select("*").from("dept") .then(function (depts){ depts.forEach((dept)=>{ //use of Arrow Function console.log({...dept}); }); }).catch(function(err) { ...
Post a Comment
Read more

How to use QueryExtenderControl in ASP.NET with LINQ

Queryextender control is a control that helps in doing actions like filtration, searching, sorting etc. on the LINQ Data source with few steps. In fact we don’t have to write any code with this. Screenshot given below is just an example that can easily be achieved through this control. In the above screenshot, we can see that there is a GridView Control that has been binded to a LINQData Source Control. And we have a DropDownlistBox that is also binded to another LINQData Source Control and displaying only grouped jobs. The GridView display all the employees who are matching the Job Parameter. This is done through QueryExtender Control. Also we can search for any name in the employee name's through Query Extender control. The code in the HTML goes like: < form id ="form1" runat ="server">     < div >         Select Job: < asp : DropDownList ID ="Job" runat ="server" DataSourceID ="LinqDataSource2...
Post a Comment
Read more