Anytime you have a specialized position, then you could see a higher rate of pay than that of a generic position such as just a plain old database developer or just developer. That's because some organizations are willing to pay a little extra to get someone in the door who can exceed at that specific set of tasks or task.

But, it's not always the case. I know in my area, all database developers who work with SQL Server are sort of expected to work in SSIS. Therefore, sometimes moving from the two titles can normally mean the same work, which means the same rate of pay depending on years of experience. The only differential here is the fact that you would be a database developer trying to fill a role for SSIS developer where your SSIS is very low. Therefore, your experience level could decrease the rate rather than increase based on a title change. But, I could be wrong.

I personally am a database developer who works with SSIS, SSRS and SSAS. I do ETL development, BI development and DW development. My title was chosen to reflect a general developer in all areas of database development as opposed to just calling me an ETL developer, BI developer or even SSIS/SSRS/SSAS developer. I didn't want employers to think that I was restricted to just one type or a limited type of skillsets with SQL Server development.

That doesn't mean that I think that I'm a master of all these areas or trying to be one. I just want the benefit to choose a direction without my title pushing me in that direction if I decide to change my mind. For example, if I was a SSIS developer for 5 years, it may be hard to convince someone that I can also do SSRS development too. But, if I was a general developer, it's a little easier to say that my role included SSRS development.