One of the most important parts of database migration is having a full understanding of the current systems and the business applications that they support. Without this fundamental knowledge, you will not only run the risk of missing key components in the system, but you will also not be able to strategically improve the performance of the database. Read More
SAP IQ 16.0 is yet another milestone in the evolution of SAP’s analytical engine that originated from Sybase IQ. SAP created entire series of how to tutorials on SAP IQ. They reach from 15.4 to 16.0 and also include SCC 3.3.
Below are a list of YouTube videos, created by SAP engineers to bring you behind the scenes of SAP IQ.
There is a total of over 30 videos available.
For Sybase IQ it is sometimes handy to reverse engineer the statements that were used to create the various IQ dbspaces. You can do this with Power Designer but not everybody has access to the tool.
Below you will find a script that does a basic attempt to reverse engineer the statements for the “create database” and “create dbspace” commands. The script is not complete with regard to all the possible options for these statements. Feel free to make adjustments or mail the author when you miss something.
NB: Written specifically for IQ 15 !
Prerequisites: Assuming you know how to decipher IQ Query Plans and understanding how Indexes use the query Engine, Parallelism and output from the Index Advisor.
IQ_SYSTEM_MAIN, IQ_SHARED_TEMP, and IQ user main dbspaces are shared by all multiplex servers, and all servers need access to the same physical file. Data managed by SQL Anywhere is not shared. Each node requires a separate copy of such data. Each server has its own set of files in IQ_SYSTEM_TEMP and IQ_SYSTEM_MSG. Read More
Parallel = the holy grail of speed! Sometimes, but in this case it does.
Why on Earth does IQ only allow you to create indexes with parallel option? Ask Sybase!
CREATE HG index idx_1_HG ON <table> (column_1);
CREATE LF index idx_2_LF ON <table> (column_2);
CREATE HG index idx_3_HG ON <table> (column_3);
...... on and on