-
Following the Hammerdb guide,I know Hammerdb does‘t support SQL server 2019 now(https://www.hammerdb.com/docs/ch01s02.html).For a simple evaluation, I try it for SQL Server 2019 , but it always occurs error,details as follow:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Although SQL Server 2019 is not listed as tested there is no known reason why it should not work correctly. Yes you would expect the dataset to be larger than 1000GB for SF1000 as you have to allow for indexes etc - in a quick test with SF1 the datafile is 2.25GB. |
Beta Was this translation helpful? Give feedback.
-
No further update, closing as error in querying the dataset build by HammerDB rather than the build itself. |
Beta Was this translation helpful? Give feedback.
Although SQL Server 2019 is not listed as tested there is no known reason why it should not work correctly. Yes you would expect the dataset to be larger than 1000GB for SF1000 as you have to allow for indexes etc - in a quick test with SF1 the datafile is 2.25GB.
The error “Arithmetic overflow error converting expression to data type int.” is an error in the query rather than the database - in this case you use the int count rather than count_big that returns bigint that you should be using. (This is used in the queries eg select o_orderpriority, count_big(*) as order_count ...)
For the error “orders ” only has one column "O_ORDERDATE" but the row count is correct - this is inconsistent …