How can we help you today? How can we help you today?

Upgrade mistake

Hi,

I mistakenly installed SQL Monitor 2.3 on the wrong box and then upgraded the database. Once I realised this I uninstalled it and upgraded the correct box.

Now the correct instance still thinks it needs to upgrade the database. Is there a way of telling it to skip this step?

Cheers,

Rhys
Rhys
0

Comments

11 comments

Sort by
  • priyasinha
    Hi Rhys,

    Did you use the existing database option when upgrading from new box? If the database is already upgraded then it wont upgrade again.

    Thanks,
    Priya
    priyasinha
    0
  • Rhys
    I did choose the existing database option. it was complaining about a duplicate index name. It's seem to run through this after another attempt but now I get an error on on each main screen / overview / alerts etc


    Procedure or function data.Cluster_StableSamples_DateRange has too many arguments specified.

    So it looks like something has gone amiss.

    Just tried a service restart and it's attempting to upgrade the database again.
    Rhys
    0
  • dlkj
    Hi Rhys,

    Please run the following query in SMMS on your SQL Monitor database and post the results:
    SELECT  Id ,
        Date ,
        CodeVersion ,
        SchemaVersion FROM versioning.SchemaVersionHistory

    Thanks,
    --
    Daniel
    dlkj
    0
  • Rhys
    As follows...

    1 2010-11-23 16:52:06.400 2.0.0.3780 Seq0
    2 2010-11-23 16:52:06.837 2.0.0.3780 Seq1
    3 2010-11-23 16:52:07.773 2.0.0.3780 Seq2
    4 2010-11-23 16:52:08.010 2.0.0.3780 Seq3
    5 2010-11-23 16:52:08.243 2.0.0.3780 Seq4
    6 2010-11-23 16:52:08.260 2.0.0.3780 Seq5
    7 2010-11-23 16:52:08.290 2.0.0.3780 Seq6
    8 2010-11-23 16:52:08.447 2.0.0.3780 Seq7
    9 2010-11-23 16:52:08.460 2.0.0.3780 Seq8
    10 2010-11-23 16:52:08.493 2.0.0.3780 Seq9
    11 2010-11-23 16:52:08.523 2.0.0.3780 Seq10
    12 2010-11-23 16:52:08.587 2.0.0.3780 Seq11
    13 2010-11-23 16:52:08.587 2.0.0.3780 Seq12
    14 2010-11-23 16:52:08.600 2.0.0.3780 Seq13
    15 2010-11-23 16:52:08.773 2.0.0.3780 Seq14
    16 2010-11-23 16:52:08.947 2.0.0.3780 Seq15
    17 2010-11-23 16:52:08.977 2.0.0.3780 Seq16
    18 2010-11-23 16:52:09.133 2.0.0.3780 Seq17
    19 2010-12-21 12:04:58.207 2.1.0.238 Seq18
    20 2010-12-21 12:04:58.690 2.1.0.238 Seq19
    21 2010-12-21 12:04:59.347 2.1.0.238 Seq20
    22 2010-12-21 12:04:59.817 2.1.0.238 Seq21
    23 2010-12-21 12:04:59.987 2.1.0.238 Seq22
    24 2011-02-18 11:47:29.310 2.2.0.260 Seq23
    25 2011-02-18 11:47:29.723 2.2.0.260 Seq24
    26 2011-02-18 11:47:30.727 2.2.0.260 Seq25
    27 2011-02-18 11:47:30.907 2.2.0.260 Seq26
    28 2011-02-18 11:47:31.197 2.2.0.260 Seq27
    29 2011-02-18 11:47:31.320 2.2.0.260 Seq28
    30 2011-02-18 11:47:49.540 2.2.0.260 Seq29
    31 2011-02-18 11:47:51.037 2.2.0.260 Seq30
    32 2011-02-18 11:47:52.383 2.2.0.260 Seq31
    33 2011-02-18 11:47:54.403 2.2.0.260 Seq32
    34 2011-02-18 11:47:54.897 2.2.0.260 Seq33
    35 2011-02-18 11:47:55.010 2.2.0.260 Seq34
    36 2011-02-18 11:47:57.020 2.2.0.260 Seq35
    37 2011-02-18 11:47:57.057 2.2.0.260 Seq36
    38 2011-05-27 12:01:57.057 2.3.0.333 Seq37
    39 2011-05-27 12:01:57.310 2.3.0.333 Seq38
    40 2011-05-27 12:01:57.513 2.3.0.333 Seq39
    41 2011-05-27 12:01:57.947 2.3.0.333 Seq40
    42 2011-05-27 12:01:58.013 2.3.0.333 Seq41
    43 2011-05-27 12:01:58.433 2.3.0.333 Seq42
    Rhys
    0
  • dlkj
    Hi Rhys,



    We have a known issue where the upgrade from 2.2 to 2.3 can get stuck. The last item in the table should be Seq50 rather than Seq42. We have a patch but it will take until early next week before we can release it.

    Luckily we have a work around you can deploy as a SQL Script. Drop me an email at daniel.kenyon-jones [AT] red-gate.com and I'll send it to you.

    You'll need to make sure you've tracked down all the instances of SQL Monitor you've installed and stop them before running the script.
    EXEC sys.sp_who2
    will show you which hosts are accessing the database.

    Cheers,
    --
    Daniel
    dlkj
    0
  • jurewwo
    Hi, my database schema upgrade gets stuck at

    The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'data.Cluster_SqlServer_Agent_Job_Keys' and the index name 'Cluster_SqlServer_Agent_Job_Keys_ParentId__Name'. The duplicate key value is (7, "Name Of A Job"). Could not create constraint. See previous errors. Warning! The maximum key length is 900 bytes. The index 'Cluster_SqlServer_Agent_Job_Keys_ParentId__Name' has maximum length of 908 bytes. For some combination of large values, the insert/update operation will fail.

    Is this something your patch is going to fix next week? Or should I do some sort of workaround?

    Thanks
    jurewwo
    0
  • priyasinha
    Hi,

    Apologies for the error. We will be releasing a patch next week. For now, I have just emailed you the workaround.

    Please let me know if you have not received my email.

    Thanks,
    Priya
    priyasinha
    0
  • mhavens
    I am also getting the same error 'jurewwo' quoted, and it is stuck at schem version 42. If I could get the email workaround as well, that would be great. Thanks!
    mhavens
    0
  • priyasinha
    mhavens wrote:
    I am also getting the same error 'jurewwo' quoted, and it is stuck at schem version 42. If I could get the email workaround as well, that would be great. Thanks!

    Hi,

    Apologies for the error. I have just emailed you workaround. Please let us know if you have not received it yet.

    Thanks,
    Priya
    priyasinha
    0
  • viralshah
    Hi Priya,

    I just upgraded to SQl monitor 2.3 my database schema upgrade gets stuck at :(

    The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'data.Cluster_SqlServer_Agent_Job_Keys' and the index name 'Cluster_SqlServer_Agent_Job_Keys_ParentId__Name'. The duplicate key value is (1, CBB55254-CCB8-4E21-80AF-8D8F54A60B77). Could not create constraint. See previous errors. Warning! The maximum key length is 900 bytes. The index 'Cluster_SqlServer_Agent_Job_Keys_ParentId__Name' has maximum length of 908 bytes. For some combination of large values, the insert/update operation will fail.

    A quick help would be Appreciated
    viralshah
    0
  • dlkj
    Hi Viral,

    We've rolled this fix into the a new release of SQL Monitor.

    Please re-download the installer from http://www.red-gate.com/products/dba/sq ... r/download

    Cheers,
    --
    Daniel
    dlkj
    0

Add comment

Please sign in to leave a comment.