С SQL Server или MySQL, если существует PK с автоматическим инкрементом, усеченным, сбросит счетчик.
There's not a lot I can tell you except "don't put a lot into your ViewState
".
Places I'd look for optimizations:
GridViews
, Lists
, and Repeaters
.GridViews
are particularly bad about ViewState
; everything you databind goes into it, so if you bind a particularly large list expecting ASP.NET to handle pagination of it for you, you're going to have a huge ViewState
. The only way to get around this is to only bind one page at a time to the GridView
, but that means you'll have to do data-side pagination which can be just as painful, or to turn off ViewState
for the GridView
, which means (arguably) useful features like in-line editing are no longer available.
There's no silver bullet here.
Вот несколько идей, как можно оптимизировать размер ViewState передается по сети ( скопировано из этого ответа ):