Blog

Clustered Index In Each Table Will Improve Your Database Performance In SQL When working with MS SQL every table should have a clustered index, preferably on the primary key field. The clustered index definition in SQL Server logically sorts the data adjacent to each other in that index key.

In many cases, we have an existing database but don’t have the original E-R diagram or physical model. Reverse Database Engineering allows us to reconstruct a physical and/or ER model from an existing schema.

This is a technique that can save you a lot of time and effort when creating Alpha Anywhere reports. No longer is there a need to create a report for every single type of scenario. We are going to show you how to create versatile reports capable of being used in many different scenarios.

Every one of us at least once had to deal with such predicament when someone accidently deletes a table without any backup to recover it. Even though you have deleted the table, you can still access the pages that are used until they get overwritten by other SQL transactions...

The Advantages of Converting from MS Access to SQL Server is that the performance, and processing time are all significantly improved.

A better solution will have a separate table so you can generate Invoice numbers. This way you let IDENTITY field work for you with any Insert as shown in the below Stored Procedure.

Microsoft changed the Identity behavior to jump in increment of 1000 or 10000 whenever the SQL Server 2012 restart. For example: we have a Primary Key that was 10012, if you re-start the SQL server instant, then in the next Insert record you will get the Primary Key as 11012.

Running any program and dealing with the UAC could be a hassle and that process also evaluates if the user has the rights to proceed with the program any further. If you need to remove the below UAC and save you the additional click then follow some basic steps to accomplish just that.