# Best approach to 50+ input sources **URL:** \ **Category:** Logstash\ **Created:** [August 17, 2020, 2:20pm UTC](https://discuss.elastic.co/t/best-approach-to-50-input-sources/245249 "2020-08-17T14:20:42Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ffknob](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ffknob/32/37008_2.png) [@ffknob](https://discuss.elastic.co/u/ffknob)\ **Post date:** [August 17, 2020, 2:20pm UTC](https://discuss.elastic.co/t/best-approach-to-50-input-sources/245249/1 "2020-08-17T14:20:42Z")
Hello I'd appreciate your thoughts on how to approcah the following use case: - I have to configure a Logstash pipeline to index a table in SQL Server - The thing is, although the table structure is the same for every client, the databases are not: each client has its own database in SQL Server - The JDBC input plugin requires a connection string, username and password to make the connection, those would be unique for every instance (client) - The statement would be the same for all of them So, how would be the best approach to this? Will Logstash scalate well? Two approaches I can think of are: 1. 50 different pipelines in `/etc/logstash/pipelines.yml`, 50 different pipeline configs, trying the most to get values from env variables (maybe only the connection credentials would differ) 2. 1 pipeline in `/etc/logstash/pipelines.yml`, but 50 inputs in the pipeline config Do you have any other suggestion? Thank you very much ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 14, 2020, 2:20pm UTC](https://discuss.elastic.co/t/best-approach-to-50-input-sources/245249/2 "2020-09-14T14:20:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.