Welcome, Guest
Username: Password: Remember me
Data Warehousing and Data integration
  • Page:
  • 1

TOPIC: New release

New release 3 months 4 weeks ago #19250

Mike,
We recently tested and are in the process of moving our servers to AWS.
We essentially did a lift and shift of our network add naming conventions.
When I started testing the ETL, none of the processes would automatically run from the scheduler
Thinking something was wrong, I installed the latest version, that did not correct the error
You logged in our system and started tracing the cause, and we traced it down to the dbo.queue or dbo.queue_actions
I think it was dbo.queue_actions andd the statuscode field was null and the sql code was looking for a zero or one.

Anyway my question is
1. We are getting closer to going live in AWS and want to have our on-prem production ready to be copied and restored to AWS
2. The restore will wipe out your corrections
3. Has the issue in the database been solved, can I download the new install and apply it to production without worry? I cannot afford for production to be down.
4. In general, I want production to be 100% good to go. Have the lift and shift happen. Be able to verify with expectations of close to perfection.

Your thought please.

Please Log in or Create an account to join the conversation.

New release 3 months 4 weeks ago #19251

  • admin
  • admin's Avatar
  • Offline
  • Moderator
  • Moderator
  • Deeds not Words
  • Posts: 7646
  • Karma: 33
  • Thank you received: 427
2. The restore will wipe out your corrections

Why it would wipe out the correction?

3. Has the issue in the database been solved, can I download the new install and apply it to production without worry? I cannot afford for production to be down.

I am really struggling to understand why you think that there is a problem with the database

Here is QUEUE table creation script.

CREATE TABLE [QUEUE] (
[QUEUE_ID] decimal(28, 0) NOT NULL ,
[OBJECT_ID] decimal(28, 0) NULL ,
[OBJECT_TYPE] decimal(28, 0) NULL ,
[OBJECT_NAME] NVARCHAR (80) NULL ,
[OBJECT_DATA] [image] NULL ,
[OBJECT_PARAMETERS] [image] NULL ,
[LOG_FILE] NVARCHAR (255) NULL ,
[LOG_DATA] [image] NULL ,
[SUBMITED] [datetime] NULL ,
[STARTED] [datetime] NULL ,
[FINISHED] [datetime] NULL ,
[STATUS] NVARCHAR (1) NULL ,
[ABORT_EXECUTION] decimal(1, 0) NULL default 0,
[USE_AGENT] decimal(1, 0) NULL default 0,
[COMPUTER_NAME] NVARCHAR (64) NULL ,
[OSUSER] NVARCHAR (30) NULL,
[TERMINATE_ON_TIMEOUT] decimal(1, 0) NULL default 0,
[EXPECTED_EXECUTION_TIME] [datetime] NULL ,
[APPLICATION_SUBMITTED] NVARCHAR (64) NULL,
[APPLICATION_EXECUTED] NVARCHAR (64) NULL,
[APPLICATION_EXECUTED_PLATFORM] NVARCHAR (30) NULL
)

Note that
[ABORT_EXECUTION] has a default 0

In your database, this default was missing and that is why the schedule was not working.
Mike

Please Log in or Create an account to join the conversation.

  • Page:
  • 1

We have 154 guests and no members online