I am a SQL 2005 newbie, but well-acquainted with SQL 2000. I am building a Data Mart ETL process that is going to be fairly small and fairly simple.
I surveyed SSIS and see that SSIS has much more capability than SQL 2000 Data Transformation Services (DTS) and is Microsoft€™s attempt at a full-featured ETL tool. It appeared I could possibly use SSIS to completely design, implement, and manage my ETL process.
We have SQL 2005 Standard Edition with Service Pack 1 applied. To further investigate SSIS capabilities, I used SSIS to design a process to populate a simple dimension table. When I use this process to populate a text file, it works fine. However, when I use the process to populate a dimension table, I get this error:
Error: 0xC113000A at Data Flow Task, Dimension Processing [772]: Errors related to feature availability and configuration: The 'Data Push' feature is not included in the 'Standard Edition' SKU.
This error seems to indicate that Standard Edition does not support populating the dimension table. However, I can find no documentation on the Internet nor any Microsoft site that further explains the specific error message above. Also, I can find little documentation about the specific SSIS restrictions that Standard Edition has in comparison to Enterprise Edition.
This experience leads me to the following questions:
1. To build an ETL process using only SSIS constructs (the €œpure-SSIS approach€?), are we going to need SQL 2005 Enterprise Edition? In other words, do you know if we will likely hit more restrictions if we continue with Standard Edition and attempt a pure-SSIS approach?
2. Does the lack of documentation about this specific error and the lack of documentation about Standard Edition SSIS specific restrictions imply SSIS is not (yet) adopted widely? (I realize it is fairly new). If we pursue the pure-SSIS approach, is it a risk that we would be somewhat on the €œbleeding edge€? and may encounter problems with little or no documentation?
3. Do you have any general thoughts on these two ETL approaches?
a. Pure-SSIS
b. Limited-SSIS plus custom non-SSIS processes
I found so many websites wrote that fuzzy grouping ,fuzzy lookup, term extraction, term lookup,Dimension processing destination adapter and Data mining model training destination adapter only available at Enterprise Edition. Anyway i still can use these components at Standard Edition. Is that any features different between these two edition for these components? Thanks
I have developed an SSIS package for ETL purpose. I am invoking the SSIS package through .Net console application by referencing the ManagedDTS Assembly. I am able to execute the package in Sql Server 2005 Developer Edition and it runs fine till completion.
But when i try to execute the packahe in Sql Server 2005 Standard edition, by invoking the package through .Net console application the status of the package is failure.
Can any one help me how to over come this problem.
I€™ve developed a BI system using the SQL Server 2005 Developer€™s Edition.
SSAS, SSIS and SSRS have been added to a SQL Server 2005 Standard Edition Server in preparation for delivering the developed database to this live environment.
So I am able to connect directly to the Database Engine, SSAS, SSIS and SSRS successfully from the actual SQL Server 2005 Standard Edition box which is sat on a Windows 2003 Server operating system.
However when I launch SQL Server Management Studio from a desk top PC which is connected to the SQL Server Standard Edition box I can€™t connect to either SSIS or SSRS, however I can connect to the Database Engine and it also seems that I can connect to SSAS OK.
I am using Windows Authentication where the I used a SQL Server account which exists with €œsysadmin€? permissions and this SQL Server account has the same login name as the Windows Server 2003 desktop login.
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
Hello!M a newbie.. I just want to know, that wots the difference b/w SQL Server Standard Edition and Express Edition.?And can I use Visual Studio 2005 (Professional Edition) with SQL Server Express Edition.?
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.
Hi all--I'm researching the cleanest downgrade path from a trial edition of SQL Server 2005 Enterprise to a licensed Standard Edition copy. It looks like downgrading will entail uninstalling the old version and installing the new version, but I'd like to save the original setup as much as possible. Detaching the old databases will preserve the non-system databases; what method would work best for restoring the system databases?
The enterprise edition of SQL server includes some advanced BI features, for example the fuzzy lookup feature of IS. If the IS package lives on an enterprise edition of SQL server and the database the package it is targeting lives on a standard edition of SQL server can the advanced features be used? Can you run a fuzzy look against a database on a standard edition of SQL server when th IS package lives on an enterprise edition of SQL server? THANKS!
I have recently upgraded a SQL x64 server from Developer Edition to Standard Edition, This succeeded without issue. Following a reboot SQL Server yielded the following message
Your SQL Server installation is either corrupt or has been tampered with unable to load SQLBoot.DLL. Please uninstall then re-run setup to correct this issue.
I'd like to upgrade from my current SQL Server version: 09.00.3042 (Workgroup edition that comes with SBS upgrade) to the standard edition that I've just purchased. I've attempted to run setup.exe SKUUPGRADE=1 from the command prompt and it just tells me that there's nothing new to install.
I don't really want to uninstall the current installation just to do something that shouldn't be complicated to do, upgrading software versions should not be a difficult process.
I believe it is possible to restore databases from Enterprise edition to an enviroment with Standard edition. We have been able to do it on databases without any partitioned tables. But if a database has partitioned tables it will not start up in the Standard edition after a successful restore. The error log states that the database will not start because partitions are not allowed in Standard edition (which we knew). But we were led to believe that the databases would restore and open fine, the partitions would just not be there in Standard edition. Are we possibly doing something wrong or will this just not work?
As an ISV, I want to certify my product on Standard Edition. I am using Developer Edition everywhere. Is there a way I can do the certification using the Developer Edition, or do I need to obtain/purchase a copy of the Standard Edition?
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.
Does anyone know if there are any issues with restoring Master DB ontoa server running Standard Edition from a server running EnterpriseEdition of SQL Server?
We have a performance problem with a SQL statement (never completes) on one of our customer€™s sites. They are running SQL Server 2005 Standard Edition with SP2. The server is dual core with 3GB or RAM.
We requested a backup of the database and restored it to a SQL Server 2005 Developer Edition Server with SP2. The server has a single CPU with 2GB or RAM. However the exact same SQL (cut and paste) executes in approx 35 seconds.
We restored the backup of the customers database SQL Server 2005 Standard Edition with SP2. The server is dual core with 2GB or RAM. However as on eth customer site the SQL never completes.
So our question is why is this happening and is there a solution?
Our understanding is that the SQL Server 2005 engine is the same but Developer Edition (aka Enterprise Edition) has additional options.
I tried to download PerformancePoint Server Trial Version to ther server today and I got to the configuration point of the Analysis Services Setting, and when I clicked next to proceed with the configuration I got a popup error message: "Microsoft Analysis Server must be Evaluation, Developer or Enterprise Edition".
Now I have SQL Server 2005 Developer Edition Disc (Bought it with Visual Studio 2005) but on the server I have SQL Server 2005 Standard Edition, if I try to run the sql server developer Edition disc, I use the wizard download and it seems that the download is going through the SQL Server entire download, it's like I'm re-downloading SQL Server all over again.
Does that seem right? what is the best approach to work around this probelm?
Hi,Is there an Upgrade path from SQl server 2000 Standard edition toEnterprise edition? DO we just have to uninstall and do a reinstall?Any help is appreciated.ThanksGG
I have a SQL Server 2005 Enterprise Edition running in a cluster environment. There is the request to Upgrade to Standard Edition. (Yes, the other way round) How can I excute an Up-/Downgrade and avoid new installation ?
We are running SQL 2000 & SP4 with our ASP.NET application, now we plan to upgrade to Enterprise Edition due to the huge diffirence in price. Can any one of u give an brief introduction of the difference between these two, and what is the advantages of enterprise edition?
Hello, pls i would like to know if i can do a full backup and recovery (with the option of restoring to a point in time) with the MS SQL Server 2000 standard edition
Hi there Our ISP hosts our data on SQL Server Enterprise, but I also going to host the databases on my local machine. As it's just local would Standard edition do? If I migrate the databases over, will it work? Thanks in advance.
We are trying to install the Standard Edition of SQL Server 2005. We already have SQL Express installed. Standard won't install and Express won't uninstall.
We have tried every suggestion we can find and some we made up. When we try to install Standard, we get to the bit where you choose what you want to install and the only thing available is workstation components.
There are so many cases of this on the Internat that I can't believe MS have not solved the issue. And I am stunned that they want to charge us more money to talk to us about how to fix something we just paid them an arm and a leg for!
What do I need to tell you to get some idea of where to go next with this?
Server OS is 2003 R2 EE x64 Sql is 2005 Std sp2 with hotfix 4 way processors 4 GB of RAM
I reading that all x32 configurations do not apply... pae , awe enabled etc....
after sp_configure ..sql is set to 2gb max memory setting. Does this not have to be increased for sql to see more memory .. I've confirmed that OS can see the 4GB but don't think SQL can.
Does 'AWE enabled' still haveto be set up (or anything else)with this setup to optimize memory.
I got a problem in my development phase. I'm developing a web-application system that running merge database technology which is centralized database and distributed database. This is because my customer want a highly optimum system standby.
My centralized database running SQL Server 2005 Standard Edition and the distributed database running SQL Server 2005 Express Edition (because it is free). Each of these database, the users can change the data on its database. So, every database must have the same data. from my understanding, each server must act as Publisher and Subscriber. Can SQL Server 2005 Express Edition be a Publisher?
If not, what the solution you all may suggest, because cost is the first factor. If my architecture is not correct, so what you all suggest to me to resolve the problem.
Thanks so much. Any suggestion and opinion is highly appreciate and I'm highly thanks to you all.
I am getting the following warning on a Live SQL 2000 system: This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 1 queries and performance may be adversely affected. Reading about this error I realised that, by mistake, the version installed is a personal edition instead of the standard edition. I am thinking to backup the databases, uninstall SQL 2000 Personal edition, install Standard edition and restore the databases back. OR, disconnect the databases, uninstall the current version, install the standard version and re-connect the databases. I haven't found within Microsoft any advice how to upgrade the personal version to the standard edition. Because it is a live system, I would not like to mess the system up. Can you please advice? Many thanks
because we installed the SQL Server 2005-64Bit Developer Edition on a 2003 Server R2-64Bit with 10GB RAM an 2 Xeon. Now we have huge performance problems wich should be better using the Stadard Edition...
I don't know if it is easily possible to upgrade by only inserting the DVD and start the Setup...
