1 year ago

#39578

test-img

mbourgon

Is using table partitioning for maintenance on tables that the service broker writes to a good or bad idea?

We have an activated stored procedure that writes errors to a table, which I recently learned is 300GB. To get rid of the 300GB I'm going to save out recent data, then truncate/reseed the table during a slow time.

For future maintenance, though, should I look at partitioning or just do periodic deletes? I can imagine a time where I try and SWITCH the partition, it waits using WAIT_AT_LOW_PRIORITY, then kills enough insert threads that the Service Broker thinks there's a poison message issue occurring, and shuts down the queue. (or it hangs, causing contention, because split/merge can't use WAIT_AT_LOW_PRIORITY).

Thanks.

sql-server

service-broker

table-partitioning

0 Answers

Your Answer

Accepted video resources