Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 27 May 2013 05:35 PM by  Ernst Peter Tamminga
SQL Azure compliant?
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages

Ernst Peter Tamminga



New Member


Posts:
New Member


--
27 May 2013 02:19 PM

    Can you make the module SQL Azure compliant?

    And make it so that the innstall pack does not generate any errors in the extension verification checker (http://evs.dotnetnuke.com)?

    0

    Steve L



    Veteran Member


    Posts:2847
    Veteran Member


    --
    27 May 2013 02:23 PM

    Hi,

    The Impersonator should be Azure compatible already as-is. Don't rely on the EVS test. The EVS test is currently malfunctioning for Azure tests as we were told by DNN Corp.

    Thanks,

    0

    Ernst Peter Tamminga



    New Member


    Posts:
    New Member


    --
    27 May 2013 04:03 PM
    slim wrote:

    Hi,

    The Impersonator should be Azure compatible already as-is. Don't rely on the EVS test. The EVS test is currently malfunctioning for Azure tests as we were told by DNN Corp.

    Thanks,


    It is NOT SQL Azure compliant. The EVS does a wonderful job for checking SQL Azure problems. I just instelled the trial on a DNN Azure install and it generates (as I expect) SQL errors:

    Start Sql execution: 01.00.00.SqlDataProvider file
    Failure SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException (0x80131904): 'Filegroup reference and partitioning scheme' is not supported in this version of SQL Server. at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection. (SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) ClientConnectionId:2aeb51e2-13e8-4944-98e5-a349ed8b5bcb -------------------- -- Schema Statements -------------------- BEGIN TRANSACTION CREATE TABLE dbo.[Revindex_Optimizer_Configuration]( [ConfigurationID] [int] IDENTITY(1,1) NOT NULL, [PortalID] [int] NOT NULL, [CreateDate] [datetime] NOT NULL, [UpdateDate] [datetime] NOT NULL, [RowVersion] [timestamp] NOT NULL, [ViewStateStorageType] [int] NOT NULL, [ViewStateStorageDuration] [int] NOT NULL, [ViewStateCompressionActive] [bit] NOT NULL, [PageTraceActive] [bit] NOT NULL, [ViewStateMinSize] [int] NULL, [ViewStateMaxSize] [int] NULL, [ViewStateStartTime] [datetime] NULL, [ViewStateStopTime] [datetime] NULL, [ViewStateActive] [bit] NOT NULL, [ViewStateTabFilter] [varchar](max) NULL, [ViewStateUrlFilter] [varchar](max) NULL, CONSTRAINT [PK_Revindex_Optimizer_Configuration] PRIMARY KEY CLUSTERED ( [ConfigurationID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] /****** Object: Index [IX_Revindex_Optimizer_Configuration] Script Date: 12/22/2012 06:39:21 ******/ CREATE UNIQUE NONCLUSTERED INDEX [IX_Revindex_Optimizer_Configuration] ON dbo.[Revindex_Optimizer_Configuration] ( [PortalID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ALTER TABLE dbo.[Revindex_Optimizer_Configuration] WITH CHECK ADD CONSTRAINT [FK_Revindex_Optimizer_Configuration_Portals] FOREIGN KEY([PortalID]) REFERENCES dbo.[Portals] ([PortalID]) ON DELETE CASCADE ALTER TABLE dbo.[Revindex_Optimizer_Configuration] CHECK CONSTRAINT [FK_Revindex_Optimizer_Configuration_Portals] -- Credit ViewState table CREATE TABLE dbo.[Revindex_Optimizer_ViewState]( [ViewStateGUID] [uniqueidentifier] NOT NULL, [Data] [varchar](max) NULL, [CreateDate] [datetime] NOT NULL, [UpdateDate] [datetime] NOT NULL, [RowVersion] [timestamp] NOT NULL, [PortalID] [int] NOT NULL, CONSTRAINT [PK_Revindex_Optimizer_ViewState] PRIMARY KEY CLUSTERED ( [ViewStateGUID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] ALTER TABLE dbo.[Revindex_Optimizer_ViewState] WITH CHECK ADD CONSTRAINT [FK_Revindex_Optimizer_ViewState_Portals] FOREIGN KEY([PortalID]) REFERENCES dbo.[Portals] ([PortalID]) ON DELETE CASCADE ALTER TABLE dbo.[Revindex_Optimizer_ViewState] CHECK CONSTRAINT [FK_Revindex_Optimizer_ViewState_Portals] COMMIT TRANSACTION
    Info End Sql execution: 01.00.00.SqlDataProvider file
    Info Finished Sql execution
    Failure Installation Failed - Script
    Info Rolling back component install - Module
    Failure ExceptionSystem.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Installer.Installers.ModuleInstaller.DeleteModule()


    2nd: the install manifest is incomplete as for the install of DLL's. Yes a bunch of dll's dropped in the bin\ for an install will work, but is incomplete as for the standard install manifest.

    0

    Steve L



    Veteran Member


    Posts:2847
    Veteran Member


    --
    27 May 2013 04:25 PM

    You posted in the wrong forum thread under Revindex Impersonator, which is a different product and that one is Azure ready. I'm going to move this thread to Revindex Optimizer.

    We just compiled and uploaded a new Optimizer version 1.1 that is Windows Azure ready. Please download it and give it try. It worked on our DNN Cloud.

    Thanks,

    0

    Ernst Peter Tamminga



    New Member


    Posts:
    New Member


    --
    27 May 2013 05:35 PM

    Sorry for posting it in the wrong forum (mouse click wrong).

    It is nog so much abotu WIndows Azure compliance, but SQL Azure compliance that was the problem. The new version installs OK.

    0
    You are not authorized to post a reply.