June 15, 2015 at 8:41 pm
Hi -
After SQL server service restart, a column which is set to auto increment jumped 1000. To fix the issue, I had to add T272 trace flag to SQL startup parameters. However, I did not see the column being reseeded after the service restart, it is still showing the 1000 jump. Am I doing something wrong?
Below the log showing the flag being added to the error log:
LogDateProcessorInfoErrorMSG
2015-06-15 22:29:53.850ServerRegistry startup parameters:
-d E:\DATA\master.mdf
-e E:\log\ERRORLOG
-l E:\DATA\\mastlog.ldf
-T 272
June 16, 2015 at 3:58 am
Try these, no gaps
-dE:\DATA\master.mdf
-eE:\log\ERRORLOG
-lE:\DATA\mastlog.ldf
-T272
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 16, 2015 at 6:35 am
Hi Perry - From the Service screen when I look at the parameter, I do not see any spaces and that is how I added it T272 without any spaces. However I see the gap when I query the error log to check for the trace. Any idea?
June 16, 2015 at 7:19 am
I can also see it from the registry screen, please see attached..
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply