Getting Data In

How to setup "Metadata" characteristics in Splunk DB connect V2, for the query results received from Microsoft SQL Server 2012?

rupesh_patil20
Path Finder

Hello,

Finally I have configure my Remote sql server database with splunk using Splunk DB connect V2, but.. in my setup of last step I really don't know what to write(fill in those fields >> http://screencast.com/t/RNqNKkvn ). For your information I have taken the screenshot which will help you to guide me.

http://screencast.com/t/0xxdLo8W > Done Name Input successfully
http://screencast.com/t/sIOhgIVFr > Choose and Preview Table successfully
http://screencast.com/t/OtezGx3nI1 > Set Parameter successfully
http://screencast.com/t/RNqNKkvn > What should I enter here in source and sourcetype?**

From SQL Server I am retrieving the data, which i want to put in the index named "dev_zipcode". This data I needed for my application.
Thanks !!
Awaited for your quick response.

0 Karma
1 Solution

laserval
Communicator

You set them to values that make it easy for you to understand where the data came from (source), and what format it is (sourcetype). So for example, I have a DB input set up where I set source to the name of the database and table, securitylogs_AccountUpdates, and I set the sourcetype to securitylogs. I then used the sourcetype to describe how to parse the timestamp in props.conf. That way, if I set up more inputs from other tables in the same database, I can use the same sourcetype so I get all that parsing done the same way.

You might not need any special parsing, so just make sure the values you put in Source and Sourcetype make sense for the future.

Here's some more info on the two concepts:

View solution in original post

0 Karma

laserval
Communicator

You set them to values that make it easy for you to understand where the data came from (source), and what format it is (sourcetype). So for example, I have a DB input set up where I set source to the name of the database and table, securitylogs_AccountUpdates, and I set the sourcetype to securitylogs. I then used the sourcetype to describe how to parse the timestamp in props.conf. That way, if I set up more inputs from other tables in the same database, I can use the same sourcetype so I get all that parsing done the same way.

You might not need any special parsing, so just make sure the values you put in Source and Sourcetype make sense for the future.

Here's some more info on the two concepts:

0 Karma

rupesh_patil20
Path Finder

Thanks Laserval.
I will do the needful as you suggested.

0 Karma

rupesh_patil20
Path Finder

Hello Friends, Please help me to solve this issue..

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...