SQL Server Integration Services (Standard Vs Enterprise Editions)
Mar 9, 2006
The advanced transforms only available with Enterprise edition:
Data Mining Training Destination
Data Mining Query Component
Fuzzy Grouping
Fuzzy Lookup
Term Extraction
Term Lookup The advanced tasks only available with Enterprise edition:
Data Mining Query Task
Now what does all of those terminologies mean above? We are trying to determine if we need to really invest in the enterprise edition for the integration services. The information I got came from:
hello all, has anyone attempted (or succesfully implemented) a solution using Standard Edition, **as a replacement** for Enterprise Edition, in a multi-partition environment?
I believe one can use external partitions in SSAS to draw data from SQL Server, I'm not sure if that's a feature that works with the Standard Ed. of SSAS.
Namely, I'd like to see if I can use a setup of 4 installs of SQL Server, Standard Edition, and use that as a feed data into SSAS Standard Edition, and save some money on licensing (probably at a cost of increased maintenance). I know that the Enterprise version also has some enhanced analytics functions and other cool stuff so that'll be lost as well, with this potential setup.
My inclination is that to use external/Remote Partitions one would still need to use the Enterprise Edition, making this the only choice, for large cube builds -- but I may be wrong.
We are going to use database mirroring and database snapshots for reporting. The principal server runs SQL Server 2005 Standard Edition and mirror (reporting) runs SQL Server 2005 Enterprise Edition (64-bit). I failed to setup database mirroring trough GUI using SQL Server Management Studio and got this error: This mirroring configuration is not supported. Because the principal server instance, <server_name>, is Standard Edition, the mirror server instance must also be Standard Edition. But when I use T-SQL commands I was able to setup database mirroring and it works OK so far. SQL BOL says that one of requirements for database mirroring is to use the same SQL Server editions but I am wondering if it works trough T-SQL why MS mention it in the requirements list, also is totally unsupported by MS?
I have been given the "Performance and Scalability Guide" for Forefront Client Security by one of our representatives from Microsoft. The document is listed as published in July 2007, so I apparently can not supply a link. The document makes a couple of hard to swallow claims, though. One of these is this:
The sizing differences between SQL Server Standard Edition and SQL Server Enterprise edition are due to the differences in the index sizes between the two editions. I have to say I do not buy this. Can anyone disillusion me, or give me a link to anything that even implies this? I have not found anything to prove or disprove this, as yet.
Another oddity in this document is that FCS will not support 64 bit SQL Server, but encourages the use of AWE and /3GB. I can not believe there are functionality differences between the two, unless their database performance is negatively impacted by the 64 bit architecture (naturally the document is silent on why they do not support 64 bit).
Anyway, the questions are does the quote above actually hold any water? And would 64 bit SQL server cause functionality problems, other than performance problems?
We are using SQL Server 2005 Standard Edition. I have SSIS package which uses 'Data Mining Query Task'. I am using this task to run the predictions using the mining model I have deployed. When I run this SSIS package from IDE , everything is fine. But I deployed this SSIS to msdb, and when I right click on the package and run it from MSDB I get error message saying ,
'Cannot run this task in this edition of Integration Services. It requires higher level edition'.
Altimately we want to execute this SSIS from an API which is written in C#. Can you please suggest any workaround for doing so?
If, in an SSIS package, you put an instance of an 'Execute SQL Task' task in the Control Flow, in the Properties window, you can see the properties of the task, for example CodePage.
If you double click on the task, the Execute SQL Task Editor appears, with several of the properties which are also in the Properties window, including CodePage.
If, in the Editor, you update the value of CodePage, then click OK, the value of CodePage in the Properties window is updated immediately.
I have written a custom SSIS task, which also has the same properties in the Properties window and in the Editor. The Editor also has an OK button. When OK is clicked, the values of the task properties are updated. An example property is FolderToArchive. If I open the Editor, change the value of FolderToArchive and click the OK button, the value of FolderToArchive in the Properties window is NOT immediately updated.
If, however, I select the FolderToArchive field in the Propertiesd window, it is then updated with the value I entered in the Editor.
How do I get my task to update the values in the Properties window, after changing a value in the Editor, when I click the OK button?
I would have thought I would need something like, in pseudo-code,
Task.Parent.PropertiesWindow.Refresh where task is of type Microsoft.SqlServer.Dts.Runtime.Task and Task.Parent is of type Microsoft.SqlServer.Dts.Runtime.Package.
I'm setting up a new system and want to do a cluster. We have Win2k3 Enterprise already. My question is do you have to have enterprise edition of SQL2K to do clustering w/ win2k3?
I have a question. I want to migrate from mySql to Sql Server, and I should decide which version will I use. The problem is that I need partitioning, and it is included only in the Enterprise version. But the Enterprise version costs 5 times more than the standard and the workgroup version. Is it worth to spend so much money only for the partitioning? Also, maybe I am wrong, and the partitioning is also included in the Standard version?
Hi, One of our main servers running on SQL Server 2000 Enterprise edition which has transactional replications on it which replicates to other servers running on the SQL Server 2000 Enterprise edition as well.
Due to Hardware problems the server is being migrated to a new machine but the client has installed SQL Server 2000 standard edition on the new machine.
We will be using a two processor cpu with 4GB RAM and we are also not planning about clustering. Is there any problem if i migrate the server in Standard Edition will the replications work properly between Standard and Enterprise editions.
What other complications can be there if i switch over to standard edition from enterprise edition
Hi My project is in .NET 2003 i.e. framework 1.1 and database in SQLServer 2000. But the reports have been developed using SQLServer 2005 Reporting Services. Now when I am trying to deploy them through deployment project of .NET its giving me following error:"Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services. Now I am really confused with this. Can any one please guide me regarding this ASAP. Thanks, Falguni
I did all the stuff necessary for the upgrading (the Upgrade Advisor didn't say anything special), but the Setup says the following:
" Name: Microsoft SQL Server 7.00.1063 Cause: The update is blocked. You can obtain more informations in the online help "Versions- and editionsupdates".
Editions problem: The update is blocked because of rules for the editions update. "
Is it possible that an upgrade is not possible with the evaluation edition? Or can there be another cause?
Is SQL Server 2000 Standard an option for a web application ? OR Only Enterprise version should be used for a web application because the standard version cannot support fully a web application?
We have installed sql server enterprise on a development box. We have decided to change to sql server standard to save money. Do we have to reinstall sql server? Or can we just change the license?
If we have to reinstall, can we do this over the sql server enterprise? Or will we need to uninstall and then install sql server standard and recreate our db's from our backup's?
Since some analysis services features are only available in Enterprise version , I have to upgrade my SQL 2005 server from standard edition to enterpise edition.
So I uninstall originial standard version of analysis service and install a Enterprise version. However, the analysis service is still a standard version after installation.
Is it possible to keep data engine as standard version and install a enterprise version of analysis service?
Hi -I have istalled sql server 2005 standard edition , I want to install sql server 2005 enterprise edition on the same machine. Is it possible? I have Microsoft windows server 2003 SP2 and 1GB RAM. I want to use partition function with the enterprise edition, will the trial version of sql server work for me? -If I have already created a database and tables using the standard edition, will I be able to access and use the database using the installed trial version or will I have to start a fresh creating a new database? - Is it possible to access the same database with any of the installed versions?
BTW, I am prety new to sql server and databases , I am trying to learn by myself
Dear All,We have a database which contains many tables which have millions ofrecords. When We attach the database with MS SQL Server 2005 StandardEdition Server and run some queries (having joins, filters etc.) thenthey take very long time to execute while when We execute same querieson Enterprise Edition then they run 10 times faster than on standardedition.Our database does not use any features which are present in EnterpriseEdition and not present in Standard Edition. We want to know what arethe differences between Standard Edition and Enterprise Edition forperformance. Why should we go for Enterprise Edition when StandardEdition has all the features required.We are presently using evaluation versions of SQL Server 2005 Standardand Enterprise Editions.Thanks and regards,Nishant Sainihttp://www.simplyjava.com
I am attempting to upgrade a 2005 Standard Edtion to Enterprise Edition. This is a default instance. All components are upgraded successfully except the Database Engine. I receive the following error:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]The certificate cannot be dropped because one or more entities are either signed or encrypted using it.. To continue, correct the problem, and then run SQL Server Setup again.
This installation does not have encryption enabled, so I do not undersand the error or how to correct it.
After rebooting the SQL instance appears to be upgraded to Enterprise, but it cannot be upgraded to SP2.
Does anyone know if it is possible to go from the Enterprise edition of SQL, back to Standard?
In other words, Enterprise Edition is installed, but what we really want is Standard. Is there any way around this, other than uninstalling and reinstalling SQL?
if one has purchased enterprise edition of sql server, could he install the standard version instead of the enterprise one without violating software license?
How are you, I was wondering if I could uninstall and reintall sql server standard and upgrade to enterprise edition.
What i mean..
We have 10 computers running sql server standard. We want to upgrade them to enterprise edition bc there are another 10 machines with enterprise.
Would we have to uninstall standard edition before installing enterprise. Or could we just install enterprise edition over standard
Has anyone done this? Compatibilty issue?? We are doing it remotly as well, some machines in NC, some in Vegas, some in Cali. So all will be done through RDC.
Here I need some help or suggestions for the following topic...
I am using SQL server 2000 enterprise edition installed on the machine. Now I wanted to change the edition from enterprise to standard. There are around 4 user databases exists on the server. What are the areas I have to take care while doing this? Could I do as normal installation? No log shipping implemented on the server.
What's the best/easiest method to upgrade from Standard Edition to Enterprise Edition and still keep the databases in tact?
My thoughts were to: 1)Backup databases 2)Detach User Databases 3)Uninstall Standard 4)Install Enterprise 5)Restore Master and msdb 6)Reattach the User Databases
Recently, I worked on installing SQL Server 2000 into a clustered environement. I installed the Standard edition, tested it, and everything works fine. However, in reading some information on Enterprise Edition from Microsoft, I see where it says to install Enterprise Edition when using a clustered, or failover, environement. Can anyone give me a layman's explanation as to why this is? Everything is functioning just fine with the Standard Edition installed.
I really don't want to re-install if I don't have to.
Does any one know if the Standard or Enterprise version of SQL Server 2K allows Maintenance Procedures like "DBCC CHECKDB REPAIR_REBUILD" to execute with users logged in, without the requirment of single user mode on the Database?
Mustrum Ridcully writes "Sitting here at work trying to figure a way to find wether SQL server is Enterprise or Standard edition. Submitting this question won't probably help much as I have to deliver report in about 30min. Nevertheless, somebody might benefit from this information in the future.
