# Snapshot gatling.conf not having jdbc tag

**URL:** <https://community.gatling.io/t/snapshot-gatling-conf-not-having-jdbc-tag/2242>\
**Category:** Gatling (Open-Source)\
**Created:** [April 28, 2015, 11:21pm UTC](https://community.gatling.io/t/snapshot-gatling-conf-not-having-jdbc-tag/2242 "2015-04-28T23:21:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![e.amitp1](https://avatars.discourse-cdn.com/v4/letter/e/3e96dc/32.png) [@e.amitp1](https://community.gatling.io/u/e.amitp1)\
**Post date:** [April 28, 2015, 11:21pm UTC](https://community.gatling.io/t/snapshot-gatling-conf-not-having-jdbc-tag/2242/1 "2015-04-28T23:21:56Z")

</div>

Any reason why the latest snapshot bundles do not have the jdbc tag which is there in the latest release version Gatling 2.1.5

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [April 29, 2015, 6:21am UTC](https://community.gatling.io/t/snapshot-gatling-conf-not-having-jdbc-tag/2242/2 "2015-04-29T06:21:28Z")

</div>

The JdbcDataWriter is going away in 2.2, for many reasons:

- It’s a pain to maintain: there’s no integration tests for it, and no core committer is interested in testing it when we release
- It’s not widely used
- It’s a perf killer under heavy load: you don’t write 10.000 records with JDBC the same way you dump 10.000 lines on a local SSD.  
If you’re interested in it, you can fork it and maintain on your side. We’ll advertise it in the third parties documentation section.

---

<div class="post-metadata">

**Author:** ![e.amitp1](https://avatars.discourse-cdn.com/v4/letter/e/3e96dc/32.png) [@e.amitp1](https://community.gatling.io/u/e.amitp1)\
**Post date:** [April 29, 2015, 7:43pm UTC](https://community.gatling.io/t/snapshot-gatling-conf-not-having-jdbc-tag/2242/3 "2015-04-29T19:43:16Z")

</div>

What about jdbc feeder which also uses the jdbc tag, is that going away as well?

jdbc {  
db {  
#url = “jdbc:mysql://localhost:3306/  
temp” # The JDBC URL used by the JDBC DataWriter  
#username = “root” # The database user used by the JDBC DataWriter  
#password = “123123q” # The password for the specified user  
}

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [April 29, 2015, 7:49pm UTC](https://community.gatling.io/t/snapshot-gatling-conf-not-having-jdbc-tag/2242/4 "2015-04-29T19:49:28Z")

</div>

No, the jdbc feeder doesn’t use anything in there.  
And it’s not going away.