SQLSERVER_8: Add Constraints after creation of table

Sometimes we forget to include constraints while a table is created. So SQL Server provides mechanism to include constraints in an already existing table. The following commands shows how to do the same:

Alter table EmpTemp add constraint Salary_check check (salary between 1000 and 5000)

In the above command we are adding a constraint “Salary_check” on table “EmpTemp” and on column “Salary” i.e. its value between 1000 and 5000 only.

Below are some commands to add constraints to an existing table.

1. Alter table temp1 add Constraint Salary_check unique(salary)

2. Alter table temp1 add constraint salary_primary primary key (salary)

3. Alter table temp1 add constraint fk_dept foreign key (Deptno) references dept(deptno)

Comments

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...

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.

How to Delete Record through Knex.

This post is all about of deleting records through KNEX ORM in Nodejs. The following code shows how to achieve this: knex("depts").where("deptno","50").del() .then(function (count) { console.log(count); }) .finally(function () { knex.destroy(); }); The above code deletes a record from a table "Depts" where Deptno = 50. It has a "then" Promise attached that will show how many records were deleted with this command. Also "finally" is the method that will always execute and will close the KNEX connection. Happy Coding !!!

Rohit Dhand

Search This Blog