Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
MarkWB
Starting Member
8 Posts |
 Posted - 2008-09-30 : 12:42:23
|
| I am working on a project in which about 150 desktops are going to be migrated from using Access with Jet SQL queries against linked SQL Server 2005 tables to a SQL Server client tool.The users are engineers in a manufacturing environment who are proficient at basic SQL to create ad-hoc queries from reporting and data warehouse DBs to pull data on manufacturing processes. They are end users, not DBAs.I am currently evaluating which client tools to use. For a variety of reasons, we have ruled out 3rd party tools - so we are going to stick with MS. As such, we are focusing on SSMSE and SSMS, both 2005 and 2008 editions.I was leaning towards SSMSE until we discovered that it does not support the Solution Explorer. A number of the stakeholders are fond of the Solution Explorer as a UI to help the users manager their .SQL files (to which their existing Jet SQL queries will be ported).Are there any implications, good or bad, to deploying the full SSMS in this environment as opposed to SSMSE?Are there any pros or cons for deploying 2008 edition client tools even though the DBs are all 2005?Any opinions would be appreciated. |
|
|
jsmaccready
Starting Member
2 Posts |
Posted - 2008-09-30 : 13:22:56
|
| Maybe you could use SQL Server Developer Edition. That would provide a license to use the SSMS interface for the "development" and management of adhoc queries (which seems to be your requirement). On the other hand, if you are running SQL Standard and have CALs for everyone, I suspect they are probably eligible to use the Mgt Studio of SS05 Std as clients. I've never seen anything in MS's licensing terms or descriptions that prohibits any CALed user from using any component of the product.The legal constraint would be that they are not allowed to create instances on their local machine. |
 |
|
|
MarkWB
Starting Member
8 Posts |
Posted - 2008-10-02 : 15:08:58
|
| Thanks, jsmaccready - yes licensing is the first thing we considered but it is a non-issue. As you say, they are all CALed, so there is no liability for using the SSMS. |
|
|
|
|
|
|
Client tools opinions