Row Generator Limit

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
ZeroPoints
Posts: 3
Joined: Tue 05 Apr 2016 02:25

Row Generator Limit

Post by ZeroPoints » Tue 05 Apr 2016 02:31

I decided to try out your software to see if i could test my home database. However i seem to have run into a problem with it only generating 86399 rows at a time even though i specified i wanted 10,000,000 as the limit returning no error message.
It goes through the generating process and at that point it switches over to inserting into database.
When it finishes it just says inserted 86399 rows into table in the general log
Is this because I'm in trial or because I've hit missed a setting somewhere?
This also happens when i do the insert into a file as well. Hits the same number of rows generated then ends.

alexa

Re: Row Generator Limit

Post by alexa » Tue 05 Apr 2016 11:59

There are no limitations in the fully featured 30-day Trial version.

Could you please provide us the CREATE definition of the table you are experiencing the issue with?

You can reply straight to our support system at supportATdevartDOTcom

ZeroPoints
Posts: 3
Joined: Tue 05 Apr 2016 02:25

Re: Row Generator Limit

Post by ZeroPoints » Tue 05 Apr 2016 21:54

So the first pk is pretty much a guid.
which is a binary(16) or (uuid() with the dashes removed)
in the generator its random by seed 1, length min:16, max:16
CREATE TABLE `test` (
`GUID` binary(16) NOT NULL,
`a` varchar(255) NOT NULL,
`b` varchar(255) DEFAULT NULL,
`c` varchar(255) NOT NULL,
`StartTime` datetime NOT NULL,
`EndTime` datetime NOT NULL,
`d` varchar(255) NOT NULL,
`e` varchar(255) DEFAULT NULL,
`f` varchar(255) DEFAULT NULL,
`g` varchar(255) DEFAULT NULL,
`h` int(11) NOT NULL,
`i` varchar(16) DEFAULT NULL,
`j` varchar(255) DEFAULT NULL,
`k` longtext,
`l` bigint(100) DEFAULT NULL,
`m` varchar(255) DEFAULT NULL,
`n` varchar(255) DEFAULT NULL,
`o` binary(16) DEFAULT NULL,
`p` varchar(255) DEFAULT NULL,
`q` varchar(255) DEFAULT NULL,
PRIMARY KEY (`GUID`,`StartTime`),
KEY `GUID` (`GUID`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

alexa

Re: Row Generator Limit

Post by alexa » Wed 06 Apr 2016 10:49

If we understood you correctly, you select only the specified table `test`, set min:16, max:16 for the column GUID and seed=1, run data insertion for 10,000,000. The insertion gets interrupted on 86399 rows.

Could you please let us know if it managed to insert 100,000?

Please also perform the following:
1. Select 'Tools -> Options' from the main menu. The 'Options' window opens.
2. Navigate to the 'Environment -> Output' branch.
3. Select the 'Write queries sent by the program to the SQL Log' and 'Log application errors' options.
4. Unselect the 'Delete application log after closing' option. Click 'OK'.
5. Reproduce the issue and send us the *.log file with the latest date from the directory

Code: Select all

%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Data Generator for MySQL\

ZeroPoints
Posts: 3
Joined: Tue 05 Apr 2016 02:25

Re: Row Generator Limit

Post by ZeroPoints » Wed 06 Apr 2016 22:34

Yep you understood.
easily reproduced for me as it keeps happening with my table


This is the file link its a 120mb log file
http://www.filedropper.com/datagenerato ... 0707-22-26


There were no errors in the log from what i saw. I did select log application errors.
If you cant access the zip with the text from that page let me know

alexa

Re: Row Generator Limit

Post by alexa » Thu 07 Apr 2016 14:20

Could you please send us the file largedataset-cache2016(10_15_15_18).dgen ?

You can send it to our support system supportATdevartDOTcom

alexa

Re: Row Generator Limit

Post by alexa » Fri 08 Apr 2016 10:38

Thank you for the reply.

Unfortunately, we haven't supported the ability to work with a composite PK yet. We are planning to support it in one of the next product versions.

Also, since there is specified in the settings for the StartTime column to generate data for a day, it's supposed to be 86400 unique records.

This can be workarounded by increasing the time interval for the column StartTime.

Post Reply