Quantcast
Viewing all articles
Browse latest Browse all 3587

Re: Performance Penatly using Partitions

>For comparison purposes I would want to see the rows from monSysStatement, the entire query plan for both queries, the output from sp_help for both tables, and information about any triggers on the tables, otherwise ...

 

Attached is the required info. nonpart_table.txt cotains sp_help and showplan for the non-partitioned table. part_table.txt cotains sp_help and showplan for the partitioned table. The output for the monSysStatement is too big to be posted directly - I can provide a ZIP file ...

 

> were these 6500 rows deleted via a single DELETE statement, or via a cursor/looping construct?  (I'm trying to understand how you could delete 6500 rows and have 6546 Transactions & Commits ... as opposed to a single Transaction & Commit.)

 

(6500 is a mistake) Each of the 6546 rows is deleted with one DELETE statement in isql. There are no transaction statements like begin transaction or commit.

 

> what construct did you use to perform the deletes? did you use a SQL batch, a stored proc, a sql query run via a exec() call?

 

The 6546 DELETE statements are generated by a csh shell script, which finally starts isql to execute the script.

 

> did you perform these deletes on the same dataserver with the same configurations

 

No, my repro was on a completely different machine. The cfg-file from the original machine is also attached in SYB.cfg.txt

 

Many thanks

 

Robert


Viewing all articles
Browse latest Browse all 3587

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>