Comments on: SQL Server: Implement Table Partition in Non Enterprise Edition (Use Partitioned View)

By: Anvesh Patel

Anvesh Patel — Wed, 08 Nov 2017 06:48:25 +0000

In reply to Kevin. Now, I have to check in detail...

By: Kevin

Kevin — Tue, 07 Nov 2017 23:07:22 +0000

Anvesh — I have the same question as O_Mine, but the link you provided doesn’t really answer the question. It shows how to put an INSTEAD OF trigger on a view, but it doesn’t provide an illustration involving a SEQUENCE. Inserting the columns from “inserted” plus the NEXT VALUE FOR [sequence] AS [ID_Column] results in 0 rows inserted every time. What are we doing wrong?

Thanks for a great article, and any help you can provide.

By: Anvesh Patel

Anvesh Patel — Mon, 23 Oct 2017 19:23:44 +0000

In reply to O Mine. Yes possible. Please visit this official - https://msdn.microsoft.com/en-us/library/def01zh2.aspx

By: O Mine

O Mine — Mon, 23 Oct 2017 18:54:43 +0000

Is there a way to also implement an “INSTEAD OF INSERT trigger” on the view that eliminates the need to specify “NEXT VALUE FOR dbo.seq_ProductHistory” in the insert statements? Trying to retrofit partitioned view onto a database with a 1TB table (not DB, table) and would like for existing code to not need to change. Existing code thinks of the ID column as an identity and doesn’t specify a value for it….