System Configuration :
OS : Windows 2003 latest SP
SQL Server : Standard Edition, SP2
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
DownTime : This is not a 24x7 kind of machine. It can have downtime
Reference : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1198044&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1026884&SiteID=1
I have been discussing this Service Broker issues in this forum for quite sometimes and sorry to bother u all again… To make things more clearer before implementing in production environment I have few doubts and it should be clarified..
As discussed in the first link we can clear sys.conversation_endpoints by just giving ALTER DATABASE GPx SETNEW_BROKERWITH ROLLBACK IMMEDIATE. But my apprehension is that if we run this command on production server and it truncate this table… what will be the impact and overall overhead on the system… Is it recommended to give this statement on Production Server daily at less traffic times, to clear this table ?… will it have adverse effect. I repeat I have downtime , I can even shutdown this server daily…
I also, just want to know why Microsoft has not looked into this aspects… why the system itself is clearing the expired messages.. What is the thought behind this architecture
I have the script to run in batch… but in high-level meetings it is always difficult to convince this architecture/process…
Thanks in advance