Messaging from several servers into a SQL Server database

We need to log user and file activity from several servers into a centralized database on a separate server.  We are trying to determine the best method to use to allow for scalability.  There may be a lot of data being logged into the database as we add the logging from additional servers.  Most of the data that is being logged would include things like user session logins and file access.

We have identified several options to send the data from each of the servers into the centralized database: SQL Server messaging, MSMQ/BizTalk, Deploy nServiceBus, WCF Routing Service, and AppFabric Service Bus.  Does anybody know of a reason that one of these approaches or something similar might be far better than any of the others to do something like this?
LesterJebsonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott PletcherSenior DBACommented:
Log locally, then use messaging or replication or some similar method to propagate the local log data to the centralized server.  You don't want to have a hard dependency on the central server.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
arnoldCommented:
Are you talking about events in the event log.

There are many different ways to propagate data, one needs to know where the data isinthe first place.

Event log/event forwarding to a central server iwith snmpmapping (evntwin) on each can ........

Does the application itself have options to generate event log, SNMP traps. ............

The growth of Db depends on the type/size and quantity..........
0
LesterJebsonAuthor Commented:
What is the best way to send messaging like this into a SQL Server database?  It looks like SQL Server has a built-in messaging feature.  Is that the best way to go for something like this?
0
LesterJebsonAuthor Commented:
Most of the data would be coming from the event logs.  We plan to turn on the Windows policies that will log user activity and file activity into the event logs.  We'll also being sending data from our FTP software logs into the SQL Server database.
0
arnoldCommented:
Are you looking to insert raw event log data

You can use event forwarding to aggregate the events to a central server and look at getting the data from the central server logged into sql
Splunk is a tool that might meet what your end goal is.
How proactive do you want it?
Combining multiple things I.e. Event forwarding, snmptrap with event to SNMP mappings, splunk.

One deals with being able to retroactively check on...
One provides immidiate ... Representation..........
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.