Home    Forums    Feature Requests    Beta Issues    SysAid Resources    Documentation    Support
Hello Guest,  Login   
        
DOWNLOAD FREE EDITION
    
     Recent Topics    Hottest Topics    Online Members    Member Listing    Advanced Search
Which Database to use when Migrating SysAid?  XML
Forum Index » SysAid Installation & Beyond
 
Author Message
Hiba
SysAider


SysAider from release 4 United Kingdom Pathfinder
Joined: 29/01/2009
Messages: 31
Location: IT Support
Offline

Hi Guys

I will soon be migrating our existing (paid for) SysAid from a domain server to another domain member server. I am aware of the procedures for this migration, however I have one question to ask....

The present SysAid uses MS-SQL. I want to install / migrate to a new domain member server and intended to use mySQL. However, as SysAid is the only application requiring a database on this server, would it not be easier to use the embedded Derby DB that comes with the application? At present we have approximataly 160 users, would the Derby DB be sufficient for this amount of users etc?

Oops that was 2 questions! sorry!! any advice on which Database to use would be most welcome.

Best regards

Hiba
BJINS
SysAid Wiz


SysAider from release 5.5 United Kingdom Pathfinder
Joined: 08/08/2008
Messages: 583
Location: United Kingdom
Offline

What is your current db size? The Derby db works fine until it reaches a size of around 4GB, so if you exceed this, then I would reccommend using an external db, such as my-SQL

M

When the going gets tough, the tough get SysAid
[MSN]
Ori
SysAid Customer Relations


Joined: 17/04/2008
Messages: 293
Location: Israel
Offline

What is your current db size? The Derby db works fine until it reaches a size of around 4GB, so if you exceed this, then I would recommend using an external db, such as my-SQL


In previous versions of Derby, it was limited up to 4GB. In the latest version, there's no limitation.

Hilba, on SMB organizations, the Derby database should be enough. If you are already using SQL as the backend, my personal advice is to stay with it since it is more stable and you can run queries directly to the database (On Derby, you need to install a third-party application).

The only thing that you need to think of is that on Derby, you can use the built-in backup utility that comes with SysAid while on external db, you need to maintain it yourself.

SysAid support.
[WWW] [MSN]
Hiba
SysAider


SysAider from release 4 United Kingdom Pathfinder
Joined: 29/01/2009
Messages: 31
Location: IT Support
Offline

Hi Guys

Thanks for the info - much appreciated...

Bjins, at present the backup for SysAid is running at 11 GB on MSSQL.

Having read your comments Ori, I will proceed with using the mySQL as the DB.

Cheers....
adrian_gazibar
SysAider

SysAider from release 5.1 Cyprus Pathfinder
Joined: 04/07/2008
Messages: 38
Offline

For 160 end-users, the database cannot be 11 Gb.
It is the MSSQL log file (.ldf) which is keeping all the transactions you ever did in the database. You can change the recovery model of the database from full to simple, then you will actually see the size of the database.
Ori
SysAid Customer Relations


Joined: 17/04/2008
Messages: 293
Location: Israel
Offline

Glad i could help you..

Just as a side note, 11GB size on your current SQL database is pretty heavy... what is the size of your LDF and MDF files? did you try to shrink your database?

SysAid support.
[WWW] [MSN]
Hiba
SysAider


SysAider from release 4 United Kingdom Pathfinder
Joined: 29/01/2009
Messages: 31
Location: IT Support
Offline

Hi guys

Thanks for the update - the 11 GB backup was the .TRN (transaction backup files) - yes, the LDF and MDF files are slightly more moderate!!

LDF = 365 MB
MDF = 4.6 MB

If I recall, we attempted to shrink this file a while ago, with no success. However, because we will be re-locating SysAid onto a new server with mySQL (instead of MSSQL) this issue should be resolved (hopefully!)

With the Backup files in mind, I am still in two minds whether to install SysAid using the embedded Derby DB or install mySQL....

Thanks anyway guys


Ori
SysAid Customer Relations


Joined: 17/04/2008
Messages: 293
Location: Israel
Offline

ohh. Now it makes sense

I think that from this point, you should get the decision yourself..
on anyway, if you do want to migrate your MS-SQL database to Derby or MySQL, you may need to contact us at helpdesk@sysaid.com and we will perform the migration for you.



SysAid support.
[WWW] [MSN]
Hiba
SysAider


SysAider from release 4 United Kingdom Pathfinder
Joined: 29/01/2009
Messages: 31
Location: IT Support
Offline

Hi Guys

I have installed a 'free' copy of SysAid onto my new server and updated this with the latest patch 6.5.08. I have decided to try the installed Derby DB instead of third party ones (MySQL).

Now, I have 'stopped the SysAid Service' and replaced the activation.xml with our present 'paid for' application .xml file. Restarted the SysAid Service and..... no SysAid!

Am I correct in assuming that the system will not activate on the new .xml information because I have it already running on another server?

I will hopefully be sending the relevant files to Ilient this weekend for migration changes (as per my message at the top of this thread)

many thanks

Hiba
itayH
SysAid Customer Relations


Joined: 23/09/2009
Messages: 1092
Offline

Hi Hiba,

You can try to use the patch that upgrade your free installation to trail\full and then use your activation.xml.
Only then you will be able to use the migrated DB.

Best Regards,
Itay
Hiba
SysAider


SysAider from release 4 United Kingdom Pathfinder
Joined: 29/01/2009
Messages: 31
Location: IT Support
Offline

Hi Itay..

I have successfully converted the 'free' version to full and used our existing activation.xml to authorise the program. Both SysAid programs are now at 6.5.08. In order to migrate our present SysAid (mssql) over to the new SysAid (Derby) I will email the following files to Ilient at close of play today:

serverConf.xml file
SysAid.ver file

fingers crossed.......

regards

Hiba
Hiba
SysAider


SysAider from release 4 United Kingdom Pathfinder
Joined: 29/01/2009
Messages: 31
Location: IT Support
Offline

Hi Guys

Getting a bit frustrated here !!

1. I have installed mySQL onto our server.
2. I then downloaded the connector (as per Ilient 'Installing the SysAid Server Locally'- Nov 09) - Renamed the .jar file as instructed to 'mysql.jar'
3. I then installed the 'free' version of SysAid (which didnt ask me what database I wanted to use) - I then upgraded the full version of SysAid over the top of the 'free' version and used our existing activation.xml (again, I wasn't asked for database selection).
4. Replaced the mysql.jar file in the deignated WEB-INF/Lib folder
5. Started SysAid (6.5.0 - Started okay but when I look in the 'about' tab I find that the database is still showing 'Derby'.

Question: Have I missed a trick here?

perhaps I need to install the full version rather than the free (but there isn't a way I can see to do this on your website)

Again, any help would inspire me to happiness !!

Many thanks

Hiba


itayH
SysAid Customer Relations


Joined: 23/09/2009
Messages: 1092
Offline

Hi Hiba,

In the free version of SysAid you can only use the embedded database which is Derby so it's skipping this step in the installation.
Please download and install the trial\full version and in the process you will be asked for DB type and according to what you choose, SysAid adjust the ServerConf.xml to the correct db type.
Another way is to edit the existing ServerConf.xml which is located at: ...\SysAidServer\root\WEB-INF\conf\
Please replace this:
<dbConf>
<dbDriver>org.apache.derby.jdbc.EmbeddedDriver</dbDriver>
<dbUrl>jdbc:derby:default</dbUrl>
<dbUser>sysdba</dbUser>
<dbPassword>masterkey</dbPassword>
<dbType>derby</dbType>
<dbEncoding>utf-8</dbEncoding>
<dbMultiply>false</dbMultiply>
<dbMainName>ilient</dbMainName>
</dbConf>

With this:
<dbConf>
<dbDriver>org.gjt.mm.mysql.Driver</dbDriver>
<dbUrl>jdbc:mysql://localhost/sysaid</dbUrl>
<dbUser>root</dbUser>
<dbPassword>password</dbPassword>
<dbType>mysql</dbType>
<dbEncoding>utf-8</dbEncoding>
<dbMultiply>false</dbMultiply>
<dbMainName>ilient</dbMainName>
</dbConf>

Restart the service.

Best Regards,
Itay
Hiba
SysAider


SysAider from release 4 United Kingdom Pathfinder
Joined: 29/01/2009
Messages: 31
Location: IT Support
Offline

Hi ItayH

Many thanks for that information (handy to know ). Fortunately, we managed to resolve the mySQL adoption, wasn't straight forward though !

We realised to install the full version (instead of the free one first), as you said it gave us the database options, so this is now resolved.

I will be emailing Ilient this weekend with our serverConf.xml file and SysAid.ver file for migration over to our new server/database. Is there any other information you will require? I will included versions of SysAid and mySQL -

Again thanks for the help

Hiba
itayH
SysAid Customer Relations


Joined: 23/09/2009
Messages: 1092
Offline

Hi Hiba,

Happy I could help And that all the info we need.

Don't forget that after you send us the DB your sever needs to be down so you want lose any SR's that will be submited at untill you receive it back.

Best Regards,
Itay
Forum Index » SysAid Installation & Beyond
Go to:   
Help Desk Software
Free Help Desk Software
Free Asset Management Software
SysAid Helpdesk Software
Web Based Help Desk Software
SysAid Help Desk Forum
General IT Discussion Forum
SysAid CSS Customer Service Software
Customer Support Software
   SysAid Technologies Ltd.
   Toll-Free phone center (U.S.): 1-800-686-7047
   Offices - U.S.617-231-0124
   Israel:+972-3-533-3675
   Skype account:ilient
   Email:helpdesk@sysaid.com
   Optimized by SEO Israel
   SysAid logos and other SysAid Technologies marks
   are trademarks or registered trademarks of
   SysAid Technologies Ltd.
   All Rights Reserved by SysAid Technologies Ltd.
   2002-2011
   Live Support Hours
   07:00 AM - 09:30 PM (UK)
   02:00 AM - 04:30 PM (EDT)

   We provide worldwide services, and we do our best
   to match the working times of customers from
   different time zones.

   SysAid Help Desk Software and Asset Management Software
Privacy Policy © Terms Of Use