Database Tuning Advisor “not permitted” error on SQL Server 2005 DE
Home > IT Answers > Security > Database Tuning Advisor "not permitted" error...
volrat
0 pts.
0
Q:
Database Tuning Advisor "not permitted" error on SQL Server 2005 DE
Security, Oracle, SQL, Servers, Microsoft Windows, DB2, Management, Database, OS, Desktops, SQL Server
Hi!

I've bought the Visual Studio 2005 Professional Edition and with it comes Visual Studio SQL Server 2005 Developers Edition. I've installed it and started developing my applications, but now when I try to tune it with the Database Tuning Advisor I get the error-message:
"Tuning this edition of SQL Server 2005 is not permitted." I've searched the net for the problem, but all I find is that DTA isn't available on the Express Edition. But I should be able to use it, shouldn't I?

BTW I had to download some file from Miscrosoft in order to get it to work. Some .dll that had to do with xml. Maybe this is the key clue...
ASKED: Nov 28 2006  10:05 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
mortree
0 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
I do NOT think the tuning will work with what MS gave developer's. Tuning is generally something that happens when developer products begin hitting the real world. I suspect that is when Microsoft expects to be paid for allowing production work to actaully begin.

Microsoft likely also thinks: As a developer on your own workstation you really don't need to tune. If your software is slow before hitting real world test loads on a setup matching an actual production server -- you need to rewrite not tune.

Between these development on your own workstation and the prodcution server, Microsoft does sell Universal Subscription Kits and such which provide special developer copies of OSes and server applications. That is you would set up actual seperate servers similar to the production network to do more elaborate testing against. These softwre products are bascially the same as prodcution software and here you would do tuning when you start sending autmated test data design to look like a full load of real users.
--

I doubt the XML intereface .dll changed the version of SQL you got. The interface components are pretty standard across versions though as you see certain SQL engine versions simply are unable to use certain features even if the interface components are not there.

You may have to contact someone on the MS usenet forums to find out for sure but -- I suspect you got the express version of SQL 2005. Something extra for free. The idea being most development works fine with Express yet most production will need a better version.
Last Answered: Nov 29 2006  6:15 PM GMT by mortree   0 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

mortree   0 pts.  |   Nov 29 2006  6:15PM GMT

I do NOT think the tuning will work with what MS gave developer’s. Tuning is generally something that happens when developer products begin hitting the real world. I suspect that is when Microsoft expects to be paid for allowing production work to actaully begin.

Microsoft likely also thinks: As a developer on your own workstation you really don’t need to tune. If your software is slow before hitting real world test loads on a setup matching an actual production server — you need to rewrite not tune.

Between these development on your own workstation and the prodcution server, Microsoft does sell Universal Subscription Kits and such which provide special developer copies of OSes and server applications. That is you would set up actual seperate servers similar to the production network to do more elaborate testing against. These softwre products are bascially the same as prodcution software and here you would do tuning when you start sending autmated test data design to look like a full load of real users.
–

I doubt the XML intereface .dll changed the version of SQL you got. The interface components are pretty standard across versions though as you see certain SQL engine versions simply are unable to use certain features even if the interface components are not there.

You may have to contact someone on the MS usenet forums to find out for sure but — I suspect you got the express version of SQL 2005. Something extra for free. The idea being most development works fine with Express yet most production will need a better version.

 
0