Note that there are some explanatory texts on larger screens.

plurals
  1. POSSMS in SQLCMD mode - Incorrect Syntax
    primarykey
    data
    text
    <p>It is my day for weird errors.</p> <p>I use a database project and as a part of Post Deployment, we use SQL Scripts to populate data in our tables. </p> <pre><code>alter authorization on database::atlas to sa; go ALTER DATABASE ATLAS SET MULTI_USER WITH ROLLBACK IMMEDIATE; GO :r C:\Scripts\Script.DisableTriggers.sql :r C:\Scripts\dbo\Script.dbo.PaymentMethod.sql :r C:\Scripts\dbo\Script.dbo.TransactionEntryMethod.sql :r C:\Scripts\dbo\Script.dbo.TransactionTypeGroup.sql :r C:\Scripts\dbo\Script.dbo.TransactionType.sql :r C:\Scripts\Script.EnableTriggers.sql </code></pre> <p>each of these scripts is very similar to the one below</p> <pre><code>SET IDENTITY_INSERT [dbo].[TransactionTypeGroup] ON INSERT INTO [dbo].[TransactionTypeGroup] (TransactionTypeGroupID,TransactionTypeGroupName) VALUES (1,'Inquiry') , (2,'Points') , (3,'Board') , (4,'Guest Meals') , (5,'Cash Equivalency') , (6,'Deposits') , (7,'Void/Void Tender') , (8,'Refund') SET IDENTITY_INSERT [dbo].[TransactionTypeGroup] OFF GO </code></pre> <p>When I get my output back, I get the following error:</p> <pre><code>(1 row(s) affected) (1 row(s) affected) (25 row(s) affected) (11 row(s) affected) (2 row(s) affected) (598 row(s) affected) (3 row(s) affected) Msg 102, Level 15, State 1, Line 234 Incorrect syntax near 'OFFSET'. </code></pre> <p>I have searched my entire SQL directory, and there is no word called OFFSET in any SQL file or in any command that I am issuing. But yet I get that error..</p> <p><strong>Msg 102, Level 15, State 1, Line 234<br> Incorrect syntax near 'OFFSET'.<br></strong></p> <p>What is going on here?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload