This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
My organization is planning an upgrade from Maximo 6 (on Oracle) to Maximo 7.6 (+ Spatial). We are investigating as part of our upgrade the option to switch from Oracle to SQL Server 2014 (or later).
Please reply back if your organization uses Maximo 7.5 or later and you either (a) considered and rejected using SQL Server, or (b) you are currently using SQL Server with Maximo 7.5 or later.
I have the following questions:
1. If you considered and rejected using SQL Server for Maximo 7.5 or later, what were your reasons?
2. If you are currently using SQL Server with Maximo 7.5 or later, how has it been working for you?
3. If you are currently using SQL Server with Maximo 7.5 or later **AND** Spatial, what issues (if any) did you encounter?
Thank you for your assistance! Bob Barker
Hi,
Majority of our clients are on Maximo 7.5 and 7.6. Most of them are using SQL server for the database.Some of them we converted from other applications into Maximo 7.5 and currently one of them has a backup database with the size of 50GB (SQL Server BAK file).They have been running fine.We have upgraded some client from Maximo version 6.x to 7.5 and 7.6. Preparation with multiple round of upgrade tests is the key to ensure a smooth upgrade.Some of the upgrade we did involved removing some of the third party add-on that the client no longer use. We clean up/remove of the custom tables and fields from the third party add-on no longer in use.
Good luck and best wishes.
KayonoCTS
From: "rbarker@dpw.lacounty.gov [MAXIMO]" <MAXIMO@yahoogroups.com>
To: MAXIMO@yahoogroups.com
Sent: Wednesday, August 19, 2015 2:26 PM
Subject: [MAXIMO List] SQL Server and Maximo 7.6 (and Spatial)
My organization is planning an upgrade from Maximo 6 (on Oracle) to Maximo 7.6 (+ Spatial). We are investigating as part of our upgrade the option to switch from Oracle to SQL Server 2014 (or later).
Please reply back if your organization uses Maximo 7.5 or later and you either (a) considered and rejected using SQL Server, or (b) you are currently using SQL Server with Maximo 7.5 or later.
I have the following questions:
1. If you considered and rejected using SQL Server for Maximo 7.5 or later, what were your reasons?
2. If you are currently using SQL Server with Maximo 7.5 or later, how has it been working for you?
3. If you are currently using SQL Server with Maximo 7.5 or later **AND** Spatial, what issues (if any) did you encounter?
Thank you for your assistance! Bob Barker
#yiv4787594960 #yiv4787594960 -- #yiv4787594960ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv4787594960 #yiv4787594960ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv4787594960 #yiv4787594960ygrp-mkp #yiv4787594960hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv4787594960 #yiv4787594960ygrp-mkp #yiv4787594960ads {margin-bottom:10px;}#yiv4787594960 #yiv4787594960ygrp-mkp .yiv4787594960ad {padding:0 0;}#yiv4787594960 #yiv4787594960ygrp-mkp .yiv4787594960ad p {margin:0;}#yiv4787594960 #yiv4787594960ygrp-mkp .yiv4787594960ad a {color:#0000ff;text-decoration:none;}#yiv4787594960 #yiv4787594960ygrp-sponsor #yiv4787594960ygrp-lc {font-family:Arial;}#yiv4787594960 #yiv4787594960ygrp-sponsor #yiv4787594960ygrp-lc #yiv4787594960hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv4787594960 #yiv4787594960ygrp-sponsor #yiv4787594960ygrp-lc .yiv4787594960ad {margin-bottom:10px;padding:0 0;}#yiv4787594960 #yiv4787594960actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv4787594960 #yiv4787594960activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv4787594960 #yiv4787594960activity span {font-weight:700;}#yiv4787594960 #yiv4787594960activity span:first-child {text-transform:uppercase;}#yiv4787594960 #yiv4787594960activity span a {color:#5085b6;text-decoration:none;}#yiv4787594960 #yiv4787594960activity span span {color:#ff7900;}#yiv4787594960 #yiv4787594960activity span .yiv4787594960underline {text-decoration:underline;}#yiv4787594960 .yiv4787594960attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv4787594960 .yiv4787594960attach div a {text-decoration:none;}#yiv4787594960 .yiv4787594960attach img {border:none;padding-right:5px;}#yiv4787594960 .yiv4787594960attach label {display:block;margin-bottom:5px;}#yiv4787594960 .yiv4787594960attach label a {text-decoration:none;}#yiv4787594960 blockquote {margin:0 0 0 4px;}#yiv4787594960 .yiv4787594960bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv4787594960 .yiv4787594960bold a {text-decoration:none;}#yiv4787594960 dd.yiv4787594960last p a {font-family:Verdana;font-weight:700;}#yiv4787594960 dd.yiv4787594960last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv4787594960 dd.yiv4787594960last p span.yiv4787594960yshortcuts {margin-right:0;}#yiv4787594960 div.yiv4787594960attach-table div div a {text-decoration:none;}#yiv4787594960 div.yiv4787594960attach-table {width:400px;}#yiv4787594960 div.yiv4787594960file-title a, #yiv4787594960 div.yiv4787594960file-title a:active, #yiv4787594960 div.yiv4787594960file-title a:hover, #yiv4787594960 div.yiv4787594960file-title a:visited {text-decoration:none;}#yiv4787594960 div.yiv4787594960photo-title a, #yiv4787594960 div.yiv4787594960photo-title a:active, #yiv4787594960 div.yiv4787594960photo-title a:hover, #yiv4787594960 div.yiv4787594960photo-title a:visited {text-decoration:none;}#yiv4787594960 div#yiv4787594960ygrp-mlmsg #yiv4787594960ygrp-msg p a span.yiv4787594960yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv4787594960 .yiv4787594960green {color:#628c2a;}#yiv4787594960 .yiv4787594960MsoNormal {margin:0 0 0 0;}#yiv4787594960 o {font-size:0;}#yiv4787594960 #yiv4787594960photos div {float:left;width:72px;}#yiv4787594960 #yiv4787594960photos div div {border:1px solid #666666;height:62px;overflow:hidden;width:62px;}#yiv4787594960 #yiv4787594960photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv4787594960 #yiv4787594960reco-category {font-size:77%;}#yiv4787594960 #yiv4787594960reco-desc {font-size:77%;}#yiv4787594960 .yiv4787594960replbq {margin:4px;}#yiv4787594960 #yiv4787594960ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv4787594960 #yiv4787594960ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv4787594960 #yiv4787594960ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv4787594960 #yiv4787594960ygrp-mlmsg select, #yiv4787594960 input, #yiv4787594960 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv4787594960 #yiv4787594960ygrp-mlmsg pre, #yiv4787594960 code {font:115% monospace;}#yiv4787594960 #yiv4787594960ygrp-mlmsg * {line-height:1.22em;}#yiv4787594960 #yiv4787594960ygrp-mlmsg #yiv4787594960logo {padding-bottom:10px;}#yiv4787594960 #yiv4787594960ygrp-msg p a {font-family:Verdana;}#yiv4787594960 #yiv4787594960ygrp-msg p#yiv4787594960attach-count span {color:#1E66AE;font-weight:700;}#yiv4787594960 #yiv4787594960ygrp-reco #yiv4787594960reco-head {color:#ff7900;font-weight:700;}#yiv4787594960 #yiv4787594960ygrp-reco {margin-bottom:20px;padding:0px;}#yiv4787594960 #yiv4787594960ygrp-sponsor #yiv4787594960ov li a {font-size:130%;text-decoration:none;}#yiv4787594960 #yiv4787594960ygrp-sponsor #yiv4787594960ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv4787594960 #yiv4787594960ygrp-sponsor #yiv4787594960ov ul {margin:0;padding:0 0 0 8px;}#yiv4787594960 #yiv4787594960ygrp-text {font-family:Georgia;}#yiv4787594960 #yiv4787594960ygrp-text p {margin:0 0 1em 0;}#yiv4787594960 #yiv4787594960ygrp-text tt {font-size:120%;}#yiv4787594960 #yiv4787594960ygrp-vital ul li:last-child {border-right:none !important;}#yiv4787594960
FWIW:
I'm trying to get to 7.6, and have been dabbling in a test system for a couple of months now. But we've used SQL Server on 6.2 for nearly a decade.
Generally, it works fine. My only real grievance with SQL Server has been that you can't search single-character "words". In Item Master, this has been a huge pain. If you are looking for a 1/4" screw, you can't just search for that in the Description field. Microsoft Full Text Search would interpret that as a 1, a /, and a 4, all being words that it would ignore when indexing, and the search would fail.
On Maximo 7.6, we'll be moving to a version of SQL Server that (finally, supposedly) gives the ability to edit its dictionary. So I should be able to tell it that 1/4 is a word that it needs to index. We're on a pretty old version of SQL Server currently, and the stopwords and dictionary are not editable.
Also, SQL Server does not support Maximo's implementation of Unicode. So, for example, I wanted to put any-or-all of the Greek alphabet symbols in a Domain, but I could not, even on the newest versions of Maximo and SQL Server.
Travis Herron
Travis: does your installation not have the Item Spec data set up? Then your users could use the specification search to find the 1/4" screw.
Shannon
Sent from my wonderful BlackBerry Z30 smartphone!
Original Message
From: therron@pcci.edu [MAXIMO]
Sent: Friday, August 21, 2015 5:56 AM
To: MAXIMO@yahoogroups.com
Reply To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] SQL Server and Maximo 7.6 (and Spatial)
FWIW:
I'm trying to get to 7.6, and have been dabbling in a test system for a couple of months now. But we've used SQL Server on 6.2 for nearly a decade.
Generally, it works fine. My only real grievance with SQL Server has been that you can't search single-character "words". In Item Master, this has been a huge pain. If you are looking for a 1/4" screw, you can't just search for that in the Description field. Microsoft Full Text Search would interpret that as a 1, a /, and a 4, all being words that it would ignore when indexing, and the search would fail.
On Maximo 7.6, we'll be moving to a version of SQL Server that (finally, supposedly) gives the ability to edit its dictionary. So I should be able to tell it that 1/4 is a word that it needs to index. We're on a pretty old version of SQL Server currently, and the stopwords and dictionary are not editable.
Also, SQL Server does not support Maximo's implementation of Unicode. So, for example, I wanted to put any-or-all of the Greek alphabet symbols in a Domain, but I could not, even on the newest versions of Maximo and SQL Server.
Travis Herron
It hadn't been invented yet back here on 6.2. But even so, Item Spec search is going to be a step harder than the simple Description search that everyone is used to in every app. I'm not saying it will be "hard" -- just "harder" than regular searching because it takes an extra button-click or two (or more).
Travis Herron