I have used SQL Server since version 6.5 and I have been a little surprised about the truth that the various tools appear to become specific to DBAs instead of designers. I loved the tranquility of and speed from the Query Analyzer for instance, but hated the built-in editor, that was really no much better than a syntax coloring-capable Notepad. Since we've Management Studio the management part appears a little better but from the developer perspective the various tools is a whole lot worse. Visual Studio's excellent text editor... without a method to personalize keyboard bindings!? Do not get me began how useless may be the tree-based management hierarchy. Why can't I re-root the tree on a listing of saved procs for instance how a Enterprise Manager accustomed to allow? Now I've got a treeview that should be scrolled flat, which causes it to be eminently useless.

The SQL server support in Visual Studio is wonderful for dealing with saved methods and processes, but it is terrible like a general random data query tool.

I have attempted various tools through the years but almost always they appear to pay attention to the management side and shortchange the developer within me. Among the finest something with fundamental admin abilities, good keyboard support and requisite DDL functionality (ideally something similar to the Query Analyzer). At this time I am seriously considering using vim+sqlcmd along with a console... I am that desperate :)

Individuals individuals who workday in and day trip with SQL Server and Visual Studio... are you finding the various tools to become sufficient? Maybe you have wanted these were better and when you have found something better, would you share please?

Thanks!

A colliege of mine swears through the SQuirreL SQL Client at http://squirrel-sql.sourceforge.net. It's free, works together with various sorts of databases, and appears enjoy it has good features. It appears like something you may be thinking about.

For ad-hoc queries, perhaps you have attempted LINQPad? It's .Internet oriented, so it might not meet your needs.

Sometimes day-in and day-by helping cover their both SQL Server Management Studio (SSMS) and Visual Studio. However, we usually use SQL claims to keep schema rather than a UI tool. Some benefits of using queries to keep schema is having the ability to look into the queries into source control and reusability in install programs. If you find any random SQL execution tool, you need to have the ability to utilize it to keep schema.

We use queries to keep our SQL Server Agent jobs.

I additionally use SSMS Activity Monitor daily. It's nice, though If only it might export and load its data.

SQuirrel is nice

I personally use SSMS solely like a developer DBA though.

From the some writers at about the time of SQL Server 2005 release complained there wasn't enough for DBAs in SSMS...

I myself stay with while using SSMS like a database dev - enhanced with SQL Prompt and SQL Search, it's really quite good for me.

Options are all around - I have never really handled to obtain totally hooked on them - but you will probably find one which suits your look and requires!

And when you are hunting for a particular item, or perhaps an SSMS add-in, this appears to become the best listing of SQL Server tools - unsure how current and current this really is, the publish comes from November 2007 - but it may be useful nevertheless: