ManageEngine ServiceDeskPlus MSP: Change Starting Request ID (Postgres)

The procedure to change the request ID for ServiceDeskPlus MSP product (v10.5 and later) is outlined below. Navigate to the location of ServiceDeskPlus MSP installation and change into the pgsql\bin directory in a command prompt. C:\ManageEngine\ServiceDeskPlus-MSP\pgsql\bin> psql -U sdpadmin -p 65432 -d servicedesk -h 127.0.0.1 Enter the password sdp@123 Queries for the respective modules: REQUEST insert into workorder(workorderid,requesterid,createdtime,respondedtime,duebytime,completedtime,timespentonreq,isparent,is_catalog_template,fr_duetime,haschange,hascausedbychange,hasproblem,surveystatus,hasdraft,resolvedtime) Continue reading →

#manageengine

ServiceDesk Plus MSP 10.5 Postgre SQL password

The latest release of ManageEngine ServiceDesk Plus MSP changes the default user and password of the Postgres SQL database. Previously, the command to connect to the database was: psql -U postgres -p 65432 -d servicedesk -h 127.0.0.1 The new change shows that there is a change in username and password as follows: psql -U sdpadmin -p 65432 -d servicedesk -h 127.0.0.1 Username: sdpadmin Password: sdp@123 Continue reading →

#manageengine

WordPress SQLite to MySQL Migration Complete

Just finished migrating my website from SQLite to MySQL. What a rush. (lol) It was actually not as bad as I thought. A lot of sed, grep and other sorcery involved; especially in transforming of SQLite statements to MySQL. Some quick commands I used: sqlite techish.db .dump > production_2018-08-23.dump.sql I found that it used quotes for tables and column names, so I had to remove those first and foremost. sed -i '/INSERT INTO/,/VALUES (/s/"//g' production_2018-08-23.dump.sql Next Continue reading →

#sqlite, #wordpress

400 Million Records in MySQL

So I'm trying to figure out a way to make searching a VARCHAR in MySQL fast when there are 400 million rows. I tried the UNIQUE approach using alter table names add unique(name(15)); in the table but I have some duplicates apparently, so now I'm trying a different method. I'm going to create multiple tables;  a-z, 0-9. Based on the input query such as SELECT * FROM name WHERE name='rich' I'll split that out and re-write the query such as SELECT * FROM r_name WHERE name='rich'. Continue reading →

SQL2008R2 Licensing Quick Reference updated (PDF)

This article was posted more than 1 year ago. Please keep in mind that the information on this page may be outdated, insecure, or just plain wrong today.

SQL2008R2_LicensingQuickReference-updated