Recently came across a limitation/issue while creating a flow to export some data from Azure SQL Server. Flow does not show table in the list if it does not have a Primary Key, so we made a DateTime field Primary Key (bad practice anyway). But it was not showing in list of list of tables.
Then came across SQL Connector Documentation and found it's limitations there. Second point under limitations says that table must have an IDENTITY column.
Limitations
The triggers do have the following limitations:
- It does not work for on-premises SQL Server
- Table must have an IDENTITY column for the new row trigger
- Table must have a ROWVERSION (a.k.a. TIMESTAMP) column for the modified row trigger
Then we changed our SQL table as below and it started showing up in the list of tables in flow:
CREATE TABLE [dbo].[abc_TriggerToRunExportUsingFlow](
[Id] [bigint] IDENTITY(1,1) NOT NULL,
[TriggerOn] [datetime] NOT NULL,
[Description] [nchar](50) NULL,
PRIMARY KEY CLUSTERED
(
[Id] ASC
)WITH (STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[abc_TriggerToRunExportUsingFlow] ADD CONSTRAINT [DF_abc_TriggerToRunExportUsingFlow_TriggerOn] DEFAULT (getdate()) FOR [TriggerOn]
GO
Really wonderful blog! It is great to see such fresh contents once in a while. Do write more such articles. Regards.
ReplyDeleteMicrosoft Dynamics CRM Training in Chennai
Microsoft Dynamics Training in Chennai
Spark Training in Chennai
Spark Training Academy Chennai
Unix Training in Chennai
Unix Shell Scripting Training in Chennai
Microsoft Dynamics CRM Training in Tambaram
Microsoft Dynamics CRM Training in Adyar
nice topic which you have choose.
ReplyDeletesecond is, the information which you have provided is better then other blog.
so nice work keep it up. And thanks for sharing.
Microsoft Dynamics AX Online Training