Reputation
Top tag
Next privilege 75 Rep.
Set bounties
Badges
4
Newest
 Benefactor
Impact
~123 people reached

  • 0 posts edited
  • 0 helpful flags
  • 13 votes cast
Nov
2
comment Best practice for application logging database replacement
I wanted to hear something not scalable way of handling these stuff, but you gave me the info of the ELK stack and more over I didn't want to see my bounty goes nowhere as the expire time is coming closer :)
Nov
2
awarded  Benefactor
Oct
27
comment Best practice for application logging database replacement
Thank you for your suggestion. Looks interesting. I have some knowledge about scaleable stuff but didn't know about the ELK stack. I'm afraid, however, that we might not be able to adapt it so easily for our apps since we need to tweak all of the apps for it and I don't think it's realistic for us. I wouldn't say taking a few secs to query something is too bad because we don't use it often but still for our mental health it would be great if it has a good performance. Also I don't think our client would be happy to introduce new cost(ELK/scale up/out) for rarely used logging search
Oct
26
awarded  Promoter
Oct
25
comment Best practice for application logging database replacement
@Bart De Vos Ah that's an interesting suggestion. Thanks. Can you elaborate more how to do 'move your datafiles with old data to other archives'? You mean detach the logging database and copy mdf and log files of SQL Sever then save somewhere? The 'large' for us is when we query something to it and takes a few secs to return then we define 'oh it is huge now'. I know we can improve querying time if we set indexes properly but we don't want to put any negative performance impact for logging. Going with azure might be considerable but I want to hear more options for now.
Oct
22
awarded  Student
Oct
22
asked Best practice for application logging database replacement
May
31
awarded  Supporter