|
From:Microsoft , Microsoft Software ,
|
See Product Page
|
User Rating: Amazon Sales Rank:#444 |
| | Page: << 1 2 3 >> |
17 of 19 customers found the following review helpful:
 Solid product - Great Price, 2006-01-30
The developer edition, to my surprise, included all of the features for me to develop enterprise level Business Intelligence projects and do some DB design work too. It integrates well with Visual Studio 2005.
When connected online, installation is easy...and it installs the prerequisites for you.
39 of 57 customers found the following review helpful:
 Good product, bad install, stupid licensing, 2006-01-03
You cannot use this product with Visual Web Developer Express. It makes you uninstall VWD(and uninstall then re-install .net 2.0) and once you install SQL 2005 you can't install VWD or any of the express products.
So your choices for asp.net developers are
A: Buy VS 2005 pro which comes with a developer copy of SQL 2005 in which case you wouldn't need this individual copy.
B: Use VWD express and SQL 2005 express, but without any of the admin tools for SQL 2005.
In short, buy this developer copy only if you plan to use some non-MS ide. The free MS editors won't work with this and the ones that cost money and work with this developer version ALREADY COME with it.
8 of 26 customers found the following review helpful:
 Very Buggy, 2005-12-26
This edition will be great, once microsoft finishes debugging it! Wait till some service packs come out before committing your critical data.
Management studio dialogs are too big to fit on the screen. I use 1024 x 768. Do they QA at all? I constantly have to resize the dialog to reach to ok button.
Editing the schema of large tables is not practical in management studio, since it uses temp tables to do every modification. Takes forever to complete, if it does n't time out and roll back first. You have to turn off the timeout in the options by setting it to zero.
Better to write an alter table command by hand, it will be much faster.
Query Tuning wizard crashed and hung in memory as soon as i opened it.
Getting my linked server to work in SQL 2005 was a pain. It won't work unless sql engine is running as local system. That is a security hole which i don't like but don't know how to fix.
Error messages are useless.
You need lots of memory for SQL. I have 2GB and it gladly uses up 1.5GB doing my queries, but that may be my query.
I would n't put this in production until a few service packs come out.
45 of 50 customers found the following review helpful:
 The easiest gets better, 2005-11-15
As a long time user of SQL Server, I was glad when Microsoft finally moved away from Sybase and started developing SQL Server on their own. Unfortunately, SQL Server 7 took a bit too long to finish and I was stuck with SQL Server 6.5.
For my Enterprise work, however, I had to move to Oracle. To embed custom code, other than T-SQL code, I was also forced to move to Oracle and Java. There was no facility in SQL Server.
With the 2000 release, SQL Server finally became a contender. With far better tools than any other RDBMS and an engine that could work well with larger databases, SQL was on the right track. It just was not quite there.
With SQL Server 2005, Microsoft finally has a real contender. First, there is a very strong database engine with features that can compete with other Enterprise level databases. While there are still some features missing, the release is fairly strong.
* Database mirroring
* Failover clustering
* Database snapshots and other recovery options
SQL Server now also offers the ability to write custom code inside the database, using any .NET language, like C# and VB.NET.
SQL Server has a few built in features that bring it up a notch, as well. The database now natively handles XML as a datatype. In addition, in supports native encryption.
For the DBA, object schemas are now separated from users, allowing you to easily move ownership away from owners who have left the company. The new schema also allows for easier security on groups of objects.
Out of the box, SQL Server has a plethora of extras that have additional cost with the competition:
* The new version of DTS, now labeled SQL Server Integration Services (SSIS) is a fully debugable ETL engine with the ability to work on multiple paths at the same time.
* Business Inteligence tools include an updated Analysis Services, the KPI (key performance indicator) framework and built in business analytics.
* Improvements to SQL Server Reporting services, including the ability to set up reporting aggregates for business users to create reports on the fly, without developer or dba time.
* SQL Server Broker - finally a easy, built in way of creating asynchronous applications in SQL Server.
On the negative, Microsoft dumped a lot of features during the beta. While I understand some of the reasons behind the removal, I would have like to have had separate date and time objects, as one example.
I also feel SQL Server Notification Services are a bit half-baked at this point in time. While much better than the version that shipped as an add-on to SQL Server 2000, they still feel a bit bolted on.
Overall, the main reason many shops will switch to SQL Server with the 2005 release comes down to ROI. With the extras out of the box, SQL Server is still a no brainer for small and medium enterprises. With this release the product is more applicable for larger enterprises, as well.
|
| Page: << 1 2 3 >> |
|