Either SQL Server Management Studio (SSMS) or Visual Studio can be used for database development. I put them side by side into a single composite screen capture where you literally see the gaps between the products. SQL Server 2012 was installed with all features selected and default settings. The only modifications to the SQL Server installation were the additions of the AdventureWorks2012 and AdventureWorks2012DW databases.
Using Visual Studio instead of SSMS for database application development gives you the advantage of integration with Team Foundation Server for source code control. Additionally, localdb gives you a way to debug stored procedures locally in case your DBA won’t grant you sufficient rights to debug on the database server. You can copy your production schema to your localdb and debug from within Visual Studio.
Figure 1. SQL Server 2012 Management Studio on the left, Visual Studio 2013 on the right. Screen captures made on Windows 8.1.