Thanks for your testing and feedback. Now a days im busy and not able to accomodate the feedback. Sorry for that.

Table partitioning feature in there in SQL Server 2008. It will appear as single table only to the application. there is not any impact on application or any database business...

please paste event log information here.

The order in which records are inserted does not hold any significance unless you specifically track the insert time details.

Also the order in which records are stored does not hold...

convert @val to varchar while concating.

It would have been very good idea if SSMS scripting utility provides option to create procedures with alter statements.

schema creation is not a very regular activity that need to be created dynamically or using procedures. Its administrative work and usually done whenever required and which is very rare....

If you want to achieve this with single table then there is possibility of implementing it using trigger.

Usually such kind of constraints are implemented using FK's and normalizing the table...

one should know the business specifications or logic to implement the functionality of calculating the salary 😎

Just try with below query if you are getting the records

SELECT PKID, ISNULL(Location,'') AS Location, ISNULL(BoardNumber,'') AS BoardNumber, ISNULL(FK_BoardSize,'') AS FK_BoardSize, ISNULL(FK_BrandId,'') AS FK_BrandId, ISNULL(FK_BrandADId,'') AS FK_BrandADId, ISNULL(FK_ProductId,'') AS FK_ProductId,...

Its difficult. :w00t:

do not understand how you want to implement unique constraint without using PK/Unique constraint? This is the simplest way than using trigger etc

You need to prepare dynamic SQL to build the delete query from the parameters you are passing to this procedure and then run the dynamic SQL using exec.

Please check the queries carefully. This should not happen. I have never seen such issue.

Replication/log shipping/mirroring is not the right option for data archival.

Recommend you to implement this through SSIS package.