Does The Sql Server 2005 EVAL Distribution Support Run Of Packages Under DtExec?
Mar 23, 2006
I believe I have made a complete install of Sql Server 2005 on my dev. machine, including all client tools, and can run SSIS packages from the dev. environment.
However DtExec refuses to run any package and always throws the "insufficient version" error (as does the "RunPackage" component, probably for the same reason).
I have repeatedly attempted to find something more to install from the Sql Server 2005 eval release that will allow DTExec to run without the "insufficient version" error, but can find nothing else to install from the eval. The install wizard (and the "change" wizard) indicates everything is installed and will not build a list of any additional components to install.
Are we sure that DtExec will install and run from a sql server 2005 eval distribution?
Licenses are in the pipeline (not that pipleine) but we need to start testing our SSIS solution in the meantime.
p.s. Kudos to the dev. team, it really is an excellent tool!
I am unclear on Microsofts policy regarding support for DTS and packages that have been imported (but not migrated) to SQL 2005.
The upgrade advisor states SQL Server 2000 Data Transformation Services Advisory SQL Server 2000 Data Transformation Services is deprecated You must completely migrate existing SQL Server 2000 Data Transformation Services (DTS) packages to SQL Server 2005 Integration Services packages before support is withdrawn.
Source Type: MSDB Package
What does this really mean? What will happen to the importing of legacy packages and this whole area within Management Studio? Will these 2005 features no longer be supported? What will happen to the Execute 2000 task? If I upgrade a SQL 2000 instance post 08/04/08 does this mean that I won't receive support from Microsoft even though the package post installation is in SQL 2005. Will the new dts designer in the feature pack be taken away/withdrawn?
To say DTS packages will no longer be supported is a very dramatic statement with far reaching consequences. How is this going to be effectively implemented? Is there really going to be no backward compatibility support in Katmai?
I have stumbled on a problem with running a large number of SSIS packages in parallel, using the €œdtexec€? command from inside an SQL Server job.
I€™ve described the environment, the goal and the problem below. Sorry if it€™s a bit too long, but I tried to be as clear as possible.
The environment: Windows Server 2003 Enterprise x64 Edition, SQL Server 2005 32bit Enterprise Edition SP2.
The goal: We have a large number of text files that we€™re loading into a staging area of a data warehouse (based on SQL Server 2k5, as said above).
We have one €œmain€? SSIS package that takes a list of files to load from an XML file, loops through that list and for each file in the list starts an SSIS package by using €œdtexec€? command. The command is started asynchronously by using system.diagnostics.process.start() method. This means that a large number of SSIS packages are started in parallel. These packages perform the actual loading (with BULK insert).
I have successfully run the loading process from the command prompt (using the dtexec command to start the main package) a number of times.
In order to move the loading to a production environment and schedule it, we have set up an SQL Server Agent job. We€™ve created a proxy user with the necessary rights (the same user that runs the job from command prompt), created an the SQL Agent job (there is one step of type €œcmdexec€? that runs the €œmain€? SSIS package with the €œdtexec€? command).
If the input XML file for the main package contains a small number of files (for example 10), the SQL Server Agent job works fine €“ the SSIS packages are started in parallel and they finish work successfully.
The problem: When the number of the concurrently started SSIS packages gets too big, the packages start to fail. When a large number of SSIS package executions are already taking place, the new dtexec commands fail after 0 seconds of work with an empty error message.
Please bear in mind that the same loading still works perfectly from command prompt on the same server with the same user. It only fails when run from the SQL Agent Job.
I€™ve tried to understand the limit, when do the packages start to fail, and I believe that the threshold is 80 parallel executions (I understand that it might not be desirable to start so many SSIS packages at once, but I€™d like to do it despite this).
Additional information:
The dtexec utility provides an error message where the package variables are shown and the fact that the package ran 0 seconds, but the €œMessage€? is empty (€œMessage: €œ). Turning the logging on in all the packages does not provide an error message either, just a lot of run-time information. The try-catch block around the process.start() script in the main package€™s script task also does not reveal any errors. I€™ve increased the €œmax worker threads€? number for the cmdexec subsystem in the msdb.dbo.syssubsystems table to a safely high number and restarted the SQL Server, but this had no effect either.
The request:
Can anyone give ideas what could be the cause of the problem? If you have any ideas about how to further debug the problem, they are also very welcome. Thanks in advance!
Hi, I'm pretty sure the answer to this is "no" but thought I'd ask anyway. Is there any way of mimicing the /Validate & /WarnAsError options of dtexec if executing a package using the object model?
If not, should I request it in the interests of consistency?
I have a SQL Server 2005 evaluation that has already been installed and setup on a server. I believe it originally had a 180 day eval. There have been numerous databases and users added as well as maintenance plan created...
The eval was put on the machine as an interim solution while waiting for paper work and order processiing things to happen. All the paperwork and ordering... have been completed and I now have the real SQL Server 2005 Standard Edition license key ....
I am very new to SQL Server and need to determine ...
1. Can I update the eval copy to become permanently licensed?
2. Would I want to upgrade the eval to permanent? Will I lose any capabilities by keeping the current eval setup?
If it is reasonable to keep the eval setup
3. How do I go about entering the license key to make it permanent?
If it is necessary to install the new Standard Edition...
4. How do I install it while maintaining the already defined databases, data, users, maintenance plan...
I had SQL Server 2005 Express originally installed and then I installed the 2005 Enterpsie 180 day Eval and for some reason I cannot get the Management Console that lets me schedule tasks to show up and the ability to do imports. The only Management console I can get to show up is that useless Management Console Express to show up. I have tried reinstalling countless times, how can I get the Management console included with the Enterprise 180 eval to show up, it seems to have been included in the install, but there are no links in the start menu for it, just the configuration tools anybody...please!
I have been running SQL Server 2005 Express with the Management Studio Express. I just downloaded and installed the Eval (Trial) version of SQL Server 2005 but have not been able to get it working. Here are a couple of questions:1. Is there a potential confict with having both versions on my machine. I don't want to uninstall express since I may have to do back to it in 180 days.2. Is there a program comparable to the Management Studio for the Eval version of SQL Server 2005?3. How do I access the Eval version? I found the folder where it installed on my C drive but don't know what to do with it.Thanks for any help you can provide.
When executing a package from Business Intelligence Studio variables are well passed between packages but when same is done using dtexec utility variables don't get passed between packages. Does anyone have any idea why this could be happening and what would be possible solutions? Thanks in advance!
Just installed SQL Server 2005 Eval version and Management Studio does not display any Import/Export functions to load data into tables of an existing database. I thought that this feature was turned off only in Management Studio Express.
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?
I have been using the 180 day evaluation version of SQL Server 2005 Standard Edition and I have my license key now for the purchased version. I read on the Microsoft site I am able to upgrade to the non-trial version without uninstalling the eval version. But for Standars Edition Microsoft states:
"... If upgrading to the fully licensed version of SQL Server 2005 Standard Edition, Workgroup Edition, or Developer Edition, it is recommended that you uninstall the 180-day trial version of SQL Server 2005 Enterprise Edition before installing the fully licensed version of the other editions..."
Is there anyway out where I don't need to uninstall my eval database server? If it is necessary to uninstall eval version, then what is the best way to preserve all my current databases?
We have been using the 180 day evaluation version and I have my license key now for the purchased version. I read on the Microsoft site I am able to upgrade to the non-trial version without uninstalling the eval version. But it doesn't tell me HOW to do it. I was expecting a menu option, maybe on the About Screen of Management Studio to enter it. (How naive is that?) Is there a simple way to tell the Eval version I am now licensed?
Is it possible to install SQL Server 2005 Eval on a Virtual PC 2007 client running Server 2008 Beta? Nothing says it isn't possible, it says I need to service pack it right away, but before it gets started it comes up with the error 'sqlcu.dll failed to load'. Anyone know what this is all about?
I'm running several SSIS-packages in stored procedure using dtexec. Actually, there is a software that is running the procedure, but that's not important here.
The problem: if some of the packages failes, the whole procedure does not fail and I don't know if all the packages are successfully completed.
Here is a sample list of ssis-packages from procedure:
Have the 2005 Enterprise Evaluation version. Trying to import data from a flat file to DB table. Tried running wizard from designer studio and from creating a data flow in SBIDS
Either way I am able to setup and start excution and then bombs with a fatal error.
"SQL Server Import and Export Wizard has encountered a problem and needs to close. We are sorry for the inconvenience."
Asks to Debug or close.. Tried installing on 2 other machines and having same issue. Tried several different data files and tables same issue.
Does anyone know if this is a bug? Am I missing something with permissions?
Our SSIS packages use the Web Service Task to call services to send email and write package failure data to a department wide database. These Web Service Calls are failing with HTTP 401 errors. It was caused by the passwords for the HTTP connections not being saved when the SSIS pkgs were saved to .dtsx files. I have tried saving the package with a password and the EncryptSensitiveWithPassword protection option. This password can be supplied when the package is called from another package or a package is executed in Visual Studio but cannot be supplied to DTexec to execute the package in a job. DTexec does have a /Password parameter but it is rejected if the package is loaded from a .dtsx file. This appears to be a bug in DTexec. It only accepts the /Password parameter when the package is loaded with the /SQL option. Specifying /Password and /File is not supported.
Is this a known bug? Are there any workarounds? Has anyone successfully called a Web Service from SSIS executed via DTexec?
1) We are migrating data from SQL Server 2000 to 2005 DB.
2) We are developing SSIS packages in client, build, deploy and install and copying to SQL Server 2005 server to execute for migration.
3) For this we encrypt all packages with password, then decrypt all while executing in a batch file using dtexec. This works fine.
4) What does not work is executing a master execute task in which are individual execute tasks. This is so since the other packages are still encrypted.
5) We decrypted them separately first using dtutil using Decrypt and Copy/Move option but while executing error is thrown that these other packages are still protected by password.
6) Do we need to decrypt, then encrypt using default package protection level and then decrypt again.
7) How exactly to just execute a master package when packages are developed on client.
Hi, what is the distribution fee for SQL Server 2005 Desktop Engine distribution? Where can I find this information? I don't need it for development only for distribution.
Using SQL Server 2005 Express (Advanced SP2) I have created a Full-Text Search application in VB for distribution on CD for single PCs. Works fine on my local machine during development.
Although the SQL Server 2005 Express edition can be distributed freely, it does not seem to support Full-Text searches in the distributed version. Is this true? Or am I missing something with my deployment?
If I need another version of Sql Server for distribution of a Full-Text Search app, how do I go about obtaining the proper DB and permission for distribution? The DB size is about 600 MB.
I am setting up a clustered sql 2005 to test replciation and I am having trouble setting the server as a distributor. I get the following message
* SQL Server could not configure xxxx as a Distributor.
Only replication jobs or job schedules can be added, modified, dropped or viewed through replication stored procedures. Changed database context to 'master'. (Microsoft SQL Server, Error: 22538)
I'm new to sql 2005 and recently installed the 180 day 2005 Enterprise Eval Product, when i click Help About in the SQL Mgnt Screen it says i have 25 days untill it expires.
The system has been setup by a freelance SQL contractor and its now live and fully working.
So i now have bought SQL 2005 Standard software and need to activate the eval product but cant figure out how to do this.
Can someone please explain my best solution here on how i can activate/license this system without loosing my data.
Hi All, I've just downloaded and installed the evaluation version of msql2005, it all seemed to go ok apart from a message towards the end of the install saying the event log was full. I cleared it an the install finished. Problem is I don't have the server manager on my menu, nor kind I find any way to run it
Since it's been about a week and I haven't gotten a response for my last question, I will restate my question here.
Should I uninstall my Visual Studio, Student Version? I had installed Visual Studio 2005, student edition, prior to installing the SQL 2005 eval. I've read that there can be a conflict with MSSQL Express which may have been installed along with my Visual Studio install as there was a SQL Configuration program on my computer before I installed the SQL 2005 trial version.
I am using MS SQL Server 2005 n Visual Studio dot net 2005, When starting the managment studio i connect using windows authentication but the problem arises when i need to open an oledbconnection via ado.net with the syntax: oconn=new oledbconnection(provider=;data source=,user id=,password equal) since windows doesnt include any password i cant use the user id and password fields which causes errors althugh i created a password for my windows account the same stuff again is there any problem to change the connection method from windows authentication to sql server authentication and how can i create a login id and password. thank you
I downloaded the 800 mb file (32bit) on my XP (SP2) box and it comes up with a message that I do not have enough disk space on c: drive. Well I have 180GB of space, so that cant be it. Is it because it requires an NTSF drive ad not a FAT32 drive?
For some reason, when I try to access a database diagram on our new 2005 SQL Server, I get the following error msg: "Database diagram support objects cannot be installed because this database does not have a valid owner" It then goes on to instruct me to either use Properties > Files or ALTER AUTHORIZATION to change the database owner. Well, I've done that - and it clearly shows that there is an owner of the database, but even if I log in as that owner, the error msg continues to come up everytime I try to access Diagrams. I found a post to run the following stored procedure which will set the sql server compatability level: EXEC sp_dbcmptlevel database_name, 90 After running that in the query window of Management Stduio, I get the following msg below on the Messages tab: "DBCC execution completed. If DBCC printed error messages, contact your system administrator." I then try to create a new diagram again, and I get the same initial error (at the top of this post). What do I need to do in order to create a DB diagram?
Hi,does anyone kown if the final release or one of the next Betas ofSQL-Server 2005 will support XQuery-Statemets including the LET-Feature.Thanks,Tobias
I am currently using SQL Server 2000 server. I have run some BCP command to import data to SQL from CSV and Text files with the help of FORMAT files through Windows Scheduler.
My doubt is, if I swich to SQL Server 2005, whether the same BCP commands will supported? If no, What are the things I need to do to run the BCP commands in 2005 as in 2000?
I heard that the BCP utility is no longer support in 2005 and this can be done thru SSIS utility. Is it right...? Is SQL Server 2005 support to use the BCP commands without going to SSIS utility?
I'm trying to ensure that the access to my symmetric key is validated every use via the use of (X.509 Certifcate) Online Certificate Status Protocol (OCSP).
Question: When a Certificate encrypted Symmetric Key is opened in SQL Server 2005, does SQL Server support OCSP revocation checking?
If it does support OCSP: Can the Certificate Revocation List Distribution Point of the certificate only contain an OCSP distribution point (instead of also including HTTP, LDAP, etc)?
This is really important as I do not want any cached CRL to authorise the access to this highly sensitive data...
Platform: - SQL Server 2005 on Windows Server 2003 R2 - Certificate Services on Windows Server 2003 R2
Refer to: USE AdventureWorks; OPEN SYMMETRIC KEY SymKeyMarketing3 DECRYPTION BY CERTIFICATE MarketingCert9; GO http://msdn2.microsoft.com/en-us/library/ms190499.aspx
I just started a new job and one of my first assignments was to determine and prove the improvement between SQL Server 2000 32 bit and SQL Server 2005 64bit extension. (Itanium may come later but for now we will live with x64)
I have used SQL 2005 before but only with a fresh install and a new application built from the ground up. Now we want to upgrade our present databases to 2k5. In a previous test by another DBA, he found the SQL 2005 ran slower. However, he realized that he was using SQL 2005 32bit on Windows 2003 64bit. Now we have everything in place, here are the steps I have accomplished so far.
Loaded Windows 2003 64 and SQL 2005 64. Made a copy of an existing database from a SQL 2000 32 bit Attached this database to the new SQL 2005 server. However, I keep the compatibility at 8.0. Updated the statistics and backed the db up. Had another DBA run a Profiler trace on the production server. Replayed the trace on the new server.
My problem is this doesn€™t seem to give the information I am looking for. First, we were only looking at queries over 5 minutes and only looking at things from a duration standpoint. We are going to change this. Second, even though I created a template that looks like the one used on the production server, it is not using it.
So how do I compare performance on this 64bit server verses the 32bit SQL 2000. Any and all help is greatly appreciated.
Looking for the best practice to upgrade a soon to expire MSSQL 2005 evaluation server to a standard production server? I understand the license requirements. I have good backups of the databases.
Should i just pop in a MVL mssql2005 cd and perform an in place upgrade? Or completely remove the eval version and install clean? Will i have to redo any SQL users i have added on this server?
Thanks for any help. If anyone has a link to a KBB article i would be happy to read that on my own as well, i just havent been able to locate one.
