New DDT Enhancements Released on 6/21/2023


Author
Message
Edhy Rijo
E
StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)
Group: StrataFrame Users
Posts: 2.4K, Visits: 23K
Hi Trent,
With the new DDT released in this link http://forum.strataframe.net/FindPost33595.aspx I noticed 2 new fields added to DBEProcedures, sp_RequiredMajorVersion, and sp_RequireVersion.  The DDT package StrataFrame.pkg provided was not working for me and I have to deploy it to another server and then compare the StrataFrame database and got the following script to add the missing fields, I hope this will help others with the same issue.

/**************************************************************************
-- -Generated by xSQL Schema Compare for SQL Server
-- -Date/Time: Jun 28 2023, 03:34:35 PM
**************************************************************************/

USE [StrataFrame]
GO

SET QUOTED_IDENTIFIER ON
SET ANSI_NULLS ON
SET ANSI_PADDING ON
SET ANSI_WARNINGS ON
SET ARITHABORT ON
SET NUMERIC_ROUNDABORT OFF
SET CONCAT_NULL_YIELDS_NULL ON
SET XACT_ABORT ON
GO

BEGIN TRANSACTION
GO

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
ALTER TABLE [dbo].[DBEProcedures] ADD [sp_RequiredMajorVersion] [int] CONSTRAINT [DF_DBEProcedures_sp_RequiredMajorVersion] DEFAULT ((0)) NOT NULL
GO

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
ALTER TABLE [dbo].[DBEProcedures] ADD [sp_RequireVersion] [bit] CONSTRAINT [DF_DBEProcedures_sp_RequireVersion] DEFAULT ((0)) NOT NULL
GO

EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Required Major Version', @level0type = 'SCHEMA', @level0name = N'dbo', @level1type = 'TABLE', @level1name = N'DBEProcedures', @level2type = 'COLUMN', @level2name = N'sp_RequiredMajorVersion'
GO

EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Require Version Indicator', @level0type = 'SCHEMA', @level0name = N'dbo', @level1type = 'TABLE', @level1name = N'DBEProcedures', @level2type = 'COLUMN', @level2name = N'sp_RequireVersion'
GO

COMMIT TRANSACTION
GO


The new fields are shown in the DDT Store Procedure Properties form as shown below. 


I have two questions:
  1. Could you please explain how these 2 options work?
  2. We will need to include the new SF assemblies v1.7.20520.1, especially the "MicroFour StrataFrame DBEngine.dll" which should be aware of these 2 new fields in the DBEProcedures, correct?
Thanks!


Edhy Rijo

Edhy Rijo
E
StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)StrataFrame VIP (3.7K reputation)
Group: StrataFrame Users
Posts: 2.4K, Visits: 23K
Edhy Rijo - 6/28/2023
Hi Trent,
With the new DDT released in this link http://forum.strataframe.net/FindPost33595.aspx I noticed 2 new fields added to DBEProcedures, sp_RequiredMajorVersion, and sp_RequireVersion.  The DDT package StrataFrame.pkg provided was not working for me and I have to deploy it to another server and then compare the StrataFrame database and got the following script to add the missing fields, I hope this will help others with the same issue.

/**************************************************************************
-- -Generated by xSQL Schema Compare for SQL Server
-- -Date/Time: Jun 28 2023, 03:34:35 PM
**************************************************************************/

USE [StrataFrame]
GO

SET QUOTED_IDENTIFIER ON
SET ANSI_NULLS ON
SET ANSI_PADDING ON
SET ANSI_WARNINGS ON
SET ARITHABORT ON
SET NUMERIC_ROUNDABORT OFF
SET CONCAT_NULL_YIELDS_NULL ON
SET XACT_ABORT ON
GO

BEGIN TRANSACTION
GO

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
ALTER TABLE [dbo].[DBEProcedures] ADD [sp_RequiredMajorVersion] [int] CONSTRAINT [DF_DBEProcedures_sp_RequiredMajorVersion] DEFAULT ((0)) NOT NULL
GO

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
ALTER TABLE [dbo].[DBEProcedures] ADD [sp_RequireVersion] [bit] CONSTRAINT [DF_DBEProcedures_sp_RequireVersion] DEFAULT ((0)) NOT NULL
GO

EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Required Major Version', @level0type = 'SCHEMA', @level0name = N'dbo', @level1type = 'TABLE', @level1name = N'DBEProcedures', @level2type = 'COLUMN', @level2name = N'sp_RequiredMajorVersion'
GO

EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Require Version Indicator', @level0type = 'SCHEMA', @level0name = N'dbo', @level1type = 'TABLE', @level1name = N'DBEProcedures', @level2type = 'COLUMN', @level2name = N'sp_RequireVersion'
GO

COMMIT TRANSACTION
GO


The new fields are shown in the DDT Store Procedure Properties form as shown below. 


I have two questions:
  1. Could you please explain how these 2 options work?
  2. We will need to include the new SF assemblies v1.7.20520.1, especially the "MicroFour StrataFrame DBEngine.dll" which should be aware of these 2 new fields in the DBEProcedures, correct?
Thanks!

Hi Trent,
Just bumping this thread since I need answers before deploying a new DDT update with my application.
Thanks!

Edhy Rijo

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search