June 18, 2013 at 12:19 am
Hi,
I need to stop a particular event "Error: 1105, Severity: 17, State: 2.
Could not allocate space for object 'dbo.XXX'.'XXXXX' in database 'XXXXX' because the 'PRIMARY' filegroup is full
" writing in SQL SErver errorlog.
Could you please let me know with the trace number which I need to use to stop the warning writing in SQL Server errorlog?
June 18, 2013 at 12:41 am
I am not sure if this could be sort of any help for you
June 18, 2013 at 12:51 am
Thanks for your reply. However I had reviewed this article before itself. but it doesn't list the trace number which need to used to this particular event
June 18, 2013 at 2:50 am
sp_altermessage 1105 , 'with_log' , 'false'
June 18, 2013 at 3:03 am
Perfect, it worked now. But to take the setting apply we need to restart the SQL SErver service
Appreciate your help
June 18, 2013 at 3:23 am
Why hide the fact that the error is occuring? Wouldn't fixing the error be a better solution?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 18, 2013 at 3:26 am
It's for one of our local old dev servers to cut short the sql error log growth.. I dont want to do it prod server
June 18, 2013 at 5:09 am
I am testing it without restarting service.It seems working. weired.
June 18, 2013 at 10:12 am
I tested it in SQL Server 2008R2 dev edition, may I changed the setting in the same query analyzer. I'll try with different server after changing the setting with new query window... and keep you posted
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy