SQL CE 3.5 Server Tools On Vista 64 - Where's IIS Backward Compatitlity Components
Mar 13, 2008
I'm trying to upgrade from the SCE 3.0 server tools to the 3.5 server tools. I've uninstalled the 3.0 tools and while trying to install the 3.5 tools I get an error on the IIS requirement indicating that with IIS 7.0 I need to install the backward compatibily components and can not proceed with the install.
Searching Microsoft I get hits that mention the IIS backward compatibility components, but no links on where to download them. This might be a useful link to add to the sticky with the downloads for SCE 3.5. Also, one of the requirements referneces on the SCE3.5 server tools download, indicates that the backward IIS compatibility components were supported on 32 bit OSs, no mention of 64; this also has me concerened.
I'm running Visual Studio 2008 and SQL Server 2005 on my workstation. My device has SCE 2.0, 3.0 & 3.5 on it; these all are working fine. I'm trying to upgrade everything to 3.5 so I can get rid of prior versions. From within VS2008 I can connect to SCE3.5 SDFs and have updated a couple of databases to 3.5. What I want to do is connect to the 3.5 SDFs from SQL Server 2005; which is why I am trying to install the server tools.
I've got SQL 2008 installed on a VM and am able to connect to 3.5 SDFs but I'm trying to avoid the hassle of firing the VM and schlepping files across the VM boundary to work with the 3.5 SDFs. It's becoming a pain. Which is why I am trying to install the server tools.
Is there a resolution to this? Can I get the server tools installed on a 64 bit Vista box? Is there a link for the backward compatibility tools?
Hi, pls can anyone help me out with this? I'm installing SQL2005 SP2 over an Itanium machine with W2003 SP2 but it keeps on failing on those features. Client components got installed with no problems. I've installed SQL2005-SP2 over x86 and x64 (not Itanium) machines many times before successfuly. I've been investigating this issue for several days with no luck so I'm a bit clueless at the moment. As I'm using Administrator account I think it is not file permission related. Summary says "Unable to install Windows Installer MSP file".
I thought I had applied sp2 successfully but I discovered when I tried to apply the hotfix ( sqlserver2005-kb933097-x86-enu.exe), that the SQL Server Tools and Workstation Components wasn't at the 3042 level.
The recommendation in the log file is to:
"Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch."
Does anyone know where I find the prerequisite patch?
Any help would be appreciated.
Regards Noel
Time: 03/13/2007 18:05:39.045 KB Number: KB933097 Machine: NOEL_EVO OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3152 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition SQL Server Database Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER SQL Server Analysis Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER SQL Server Reporting Services 2005 (SQL2005) ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Notification Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Integration Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Tools and Workstation Components 2005 ENU SP1 9.1.2153 x86 DEVELOPER
********************************************************************************** Products Disqualified & Reason Product Reason SQL Server Tools and Workstation Components 2005 The product instance SQL Tools does not have prerequisite update 3042 installed. Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation.
We've been trying to use CozyRoc components in SQL server Data Tools. It seems like way to insert Cozy Components has been changed for SSDt as we're not getting CHOOSE ITEMS option in ToolBox(Right Click on Toolbox).link or Video where SSDT was used to Cozy Components.
I have installed successfully Microsoft SQL server 2005 in MSCS.
However the set up did not install Workstation components (client tools - SSMS etc).
I have successfully installed workstation components in one node of cluster.
However setup is giving following error while installing workstation components on other node. (From this node MS SQL server 2005 was installed).
Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
I did "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, /setup".
It executed but no error, no output.
Any gues, help in isolating issue?
Any more information required.(Media is ok. Setup has been tried after reboot. There is enough disk space.)
Regards.
Mahesh =========== Setup
1) Microsoft Cluster of two nodes. 2) Hardare - HP Blade servers 3) OS - Windows 2003 EE with SP2 4) SQL Server 2005 Standard Edition with SP2.
=============================
MSI (s) (B0:7C) [17:40:20:390]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup MSI (s) (B0:7C) [17:47:23:609]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
MSI (s) (B0:7C) [17:47:35:921]: Note: 1: 1729 MSI (s) (B0:7C) [17:47:35:921]: Product: Microsoft SQL Server 2005 Tools -- Configuration failed.
MSI (s) (B0:7C) [17:47:35:953]: Cleaning up uninstalled install packages, if any exist MSI (s) (B0:7C) [17:47:35:953]: MainEngineThread is returning 1603 MSI (s) (B0:A0) [17:47:36:062]: Destroying RemoteAPI object. MSI (s) (B0:80) [17:47:36:062]: Custom Action Manager thread ending.
I am having problems installing the SQL Server Compact Server Tools on my Vista laptop to allow me to connect my Mobile Device running SQL Server Compact directly to my SQL Server 2005 database through IIS.
I have done this successfully with an XP machine so I'm not sure if it is Vista problem or not.
I have installed SQL Server 2005 SP2. When I try to install the replication server tools (Sqlce30setupen.msi), in "System Configuration Check" window I get a failure on "SQL Server requirement" that says: "You must first install the Replication Components for SQL Server 2000 SP 3a or higher or the SQL Server 2005 Replication Components" and the client components are full instaled in my computer.
When I install SQL Server 2005, it all goes well except that it fails to install these two:
- SQLXML 4
- workstation components and tools
When I try to install these two from the CD in the Setup folder of the CD 2 with the files sqlxml4.msi and sqlRun_Tools.msi (if I remember these names correctly), it gives me an error:
'Ce package d'installation n'est pas pris en charge par ce type de processeur'
Sorry. My SQL CDs are in french, but it roughly translates to the message:
This installation package is not taken by this processor.
I thought that my hardware configuration does not meet the requirements. But I have a Pentium 4, 2Gig RAM, over 100Gig free HD space. Also I tried to install on other computers to no avail. This is a fresh install, that is, there is no previous SQL Server 2000 in it, no VS.NET 2005 or before. Nothing. I have just a fresh, new computer.
I am having trouble installing disc number 2 on sql standard 2005( I installed disc one) I get the message my workstation components are already installed etc.It will not allow me to go any further It seem like everything installed Here is my summary.... I unistalled vs 2 express 2005---I never used it...... Here is my list on my vista ultimate computer sql server business intelligence, sql server management studio, analysis services installed configuration tools documentation pefmorance tools Did I need to install disc 2 instead of disc 1? one I am using vista Please help ? I tried opening business intelligence studio it says it has compability issues Here is my log: Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Professional (Build 6000) Time : Tue Apr 29 14:13:59 2008
Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_3.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_3.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_3.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_4.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_4.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_4.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_5.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_3.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_5.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_5.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLSupport_6.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLNCLI_4.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Visual Studio 2005 Premier Partner Edition - ENU Product Version : 8.0.50727.42 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_PPESku_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_OWC11_6.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BOL_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_BackwardsCompat_6.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Integration Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_DTS.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLXML4_1.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQL.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_SQLXML4_2.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Analysis Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_AS.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Notification Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_NS.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Reporting Services Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_RS.log -------------------------------------------------------------------------------- Machine : BILLPREC690 Product : Microsoft SQL Server 2005 Tools Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_BILLPREC690_Tools.log --------------------------------------------------------------------------------
have removed bsn contact manager and all sql related files from previous installation attempts, rebooted so should be a clean install - but still it fails
what did I miss or what am I doing wrong?
here are the logs with ref to the two items that fail
~~~
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Professional (Build 6000) Time : Tue Mar 20 18:30:20 2007
Product : OWC11 Error : Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:Program FilesMicrosoft OfficeOFFICE111033SETUP.CHM. --------------------------------------------------------------------------------
Product : Microsoft Office 2003 Web Components Product Version : 11.0.8003.0 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_PATRICES-XPS_OWC11_1.log Last Action : InstallExecute Error String : Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:Program FilesMicrosoft OfficeOFFICE111033SETUP.CHM. Error Number : 1706
thanks for any help/light/suggestions you can share
I am running a SQL Server 2000 enterprise default instance and SQL Server 2005 standard named instances on a machine. I uninstalled the default instance and tried to instance 2005 but was unable to with the error:
'an installation packages for the product Microsoft SQL Server Backward Compatibility cannot be found. Try the installation again using a valid copy of the installation packages sqlserver2005_bc.msi'
I have tried to repair the backward compatibility currently installed and have also tried runing the msi file again but it will not install.
I have also put back 2000 as the default instance. then tried to apply sp1 to the 2005 named instances and i cannot do that either. anyone have any ideas?
Login failed for user 'TOSHIBA-USERASPNET' I know that the file persmission for the web application have to include aspnet, so i keep resetting the folder permission for aspnet in file manager, but the login failed keeps coming back every day or two problem is after working with VS05 Pro, SQL Server Management Studio CTP, somehow the aspnet persmission get changed, use alot of sqldatasource wizards and often there is a conflict/hang between the datasource wizard and the need to have the mdf in a dettached state within VS server explorer, not sure but the procedure to fix this seems to be to reboot, detach and re-attach the mdf in the Sql server Studio tool, re-apply the aspnet file permission on the web app folders (wonder should i be doing this in IIS instead), make sure the mdf within server explorer is detached, the it works anyway, getting real tired of the resulting delays and design time derailment, clues greatly appreciated, thanks sometimes i can use View in Browser when in VS05 form view and i wont get the aspnet folder permission error and other times i do. last thing, is it a bad idea to give aspnet full permission for the entire web applicaiton??
Everything I've read says that custom data flow components are built by inheriting from the Microsoft.SqlServer.Dts.Pipeline.PipelineComponent class.
But the stock components such as the Derived Column data flow transformation must each be implemented by their own class. So how do I base my custom components on those classes? The documentation for the PipelineComponent class doesn't list any such subclasses.
Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?
05/19/2006 08:58:27.648 ================================================================================ 05/19/2006 08:58:27.648 Hotfix package launched 05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client 05/19/2006 09:00:04.383 Attempting to install target: CLARITY 05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi 05/19/2006 09:00:04.399 Attempting to install file: \<server>s$917f50731dade382ab1bHotFixSqlncliFilessqlncli.msi 05/19/2006 09:00:04.399 Creating MSI install log file at: C:WINDOWSHotfixRedist9LogsRedist9_Hotfix_KB913090_sqlncli.msi.log 05/19/2006 09:00:04.415 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 05/19/2006 09:00:04.415 Failed to read registry key: Debug 05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0. 05/19/2006 09:00:51.118 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 05/19/2006 09:00:51.118 Failed to read registry key: Debug 05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \<server>s$917f50731dade382ab1bHotFixSqlncliFilessqlncli.msi 05/19/2006 09:00:51.134 Successfully installed target: <SERVER> 05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client 05/19/2006 09:00:51.134 05/19/2006 09:00:51.134 Product Status Summary: 05/19/2006 09:00:51.134 Product: SQL Server Native Client 05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required 05/19/2006 09:00:51.134 05/19/2006 09:00:51.134 Product: Setup Support Files 05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied 05/19/2006 09:00:51.150 05/19/2006 09:00:51.150 Product: Database Services 05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.150 05/19/2006 09:00:51.150 Product: Notification Services 05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.150 05/19/2006 09:00:51.150 Product: Integration Services 05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.150 05/19/2006 09:00:51.150 Product: Client Components 05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.165 05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser 05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied 05/19/2006 09:00:51.165 05/19/2006 09:00:51.165 Product: SQLXML4 05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied 05/19/2006 09:00:51.165 05/19/2006 09:00:51.165 Product: Backward Compatibility 05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied 05/19/2006 09:00:51.181 05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer 05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied 05/19/2006 09:00:51.181
In another thread Jamie Thomson very informatively said "The components in SSIS are deliberately atomic (i.e. they do something very specific) so that its easy to put them together to build something greater than the sum of the parts". Which does make a lot of sense. However, I've been finding that I end up having to create exactly the same "pattern" of combined transform components again and again in order to solve the same problem but in different dataflows (or even within the same dataflow). Cut-and-paste-tastic! In order to obtain real re-use, it seems to me like SSIS is crying out for an easy way to create new components by using composition - i.e. the ability to take commonly-used combinations of existing components and create new "super" components (without having to write Custom Transform Components in C#/VB.Net and handle everything in code).
Does anyone know if this sort of functionality is likely to make it into SSIS in the forseeable future?
I get the impression that osql (or somewhere in the sql processing) precompiles the entire script before it executes anything. In particular, this is a problem because it means you can't use IF statements to bracket new features in a script designed to be run on both old and new versions of SQL Server. I'm trying to handle an issue whereby I need to use "CREATE LOGIN" on SQL Server 2005 because I need to set CHECK_POLICY = OFF, and you can't do that with sp_addlogin. However, on SQL Server 2000, while I can't use CREATE LOGIN, I don't need to because the default password policy is such that the password being used does not fail without it (as it does in SQL Server 2005, and is why we need to set CHECK_POLICY), so I can simply use sp_addlogin to create the user w/o a CHEC_POLICY setting.
It appears however, due to the way that SQL is processed, it is impossible to create an SQL script of this nature that will work under both SQL Server 2000 and SQL Server 2005. I added code to check the Product Version, and can successfully bracket the code necessary with IF statements, but even though the IF statement would cause the CREATE LOGIN code to not be executed on SQL Server 2000, it errors anyway apparently because it is preparsing the script and of course, SQL Server 2000 doesn't have CREATE LOGIN. Consequently, checking Product Version is useless in this case. It looks like we'll have to do the version check outside of SQL and invoke script A for SQL Server 2000 and script B for SQL Server 2005.
Unless that is, I misunderstand the error I get from SQL Server 2000, or if there's some other way to compatibly do such a conditional. Here's an example script that runs fine under SQL Server 2005:
--------------- declare @ProductVersion as integer set @ProductVersion = cast(left(cast(serverproperty('productversion') as varchar(30)),1) as integer)
print 'Product Version = ' + cast(@ProductVersion as char)
IF @ProductVersion < 9 exec sp_addlogin 'testuser', 'fubar', 'master' IF @ProductVersion > 8 BEGIN CREATE LOGIN testuser WITH PASSWORD = 'fubar', CHECK_POLICY = OFF, DEFAULT_DATABASE = [master] END ----------------
On SQL Server 2000, @ProductVersion gets set to 8, but I get the following error:
Msg 170, Level 15, State 1, Server TESTSVR, Line 10 Line 10: Incorrect syntax near 'LOGIN'.
We have two different machines in different locations running SQL2000. One was upgraded to SQL2005. The problem is we can't upgrade the other at the moment cause it is running SBS2003 (requires alot more planning), But we would like to get information from the computer running SQL2005. Is there a patch that can be obtained so that we can open the database created using SQL2005 in SQL2000? We desperately need the database and upgrading to SQL2005 with SBS2003 is not straight forward.
Does anyone know if the enhanced data types (character length up to 8,000 bytes for some types) and the increase in the number of tables used in joins are available when using the 65 backward compatibility mode?
As our application is going to be closed in few months and for testing purpose
we decided to continue running dts packages in SQL server 2005. As part of upgrade we are migrating all others( Databases, OLAP and Reporting Services). We have created SSAS 2005 cubes which we want to process using Analysis Services 2000 Processing Task in DTS. Is this possible? If not possible, Our organization need a confirmation from a Microsoft manual that it cannot.
The link about backward compatibility describes about using SQL 2005 datasources in DTS and editing Analysis Services Processing Task with SQL Server 2000 Analysis Services installed. However it does not mention anything about support for processing SSAS 2005 cubes with the help of Analysis Services 2000 Processing task. Would you please provide a link which gives a description about this.
The installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
I am running SQL Server 2005 x64 Enterprise under Windows 2003 x64 Enterprise. My current backup strategy uses T-SQL jobs run by SQL Agent (writes out *.bak files) and then I have an Integration Services job that copies the *.bak files to our NAS device. I have performed a restore without issue. The jobs are all automated every four hours via SQL Agent. Is this a sound strategy or are there additional benefits to using 3rd party tools? If so, what are the advantages and which tool provides them?
I get the following error. Err.Description - "Rowset does not support fetching backward." Err. Number - -2147217884
Can somebody tell me the reason behind this error.
My Reasearch: I have got to know that I get this error in the line of code recordset.MoveLast in My code.
My Code environment: I have built an SQL Query string which calls the Strored procedure with one parameter (parameter tyoe is string type). I have attached the SP code below.
and SP contains the call for querying other database in the same server using OPENQUERY command.
and the VB code contains code as Recordset.MoveLast. (Error is generated here and Recordset.RecordCount is also -1)
AS BEGIN DECLARE @sSQL VARCHAR (1000) SET @sSQL = '''SELECT * FROM VW_JOKE WHERE JOKE_ID = ''' + '''' + @sRMS_Status + '''' + ''' ORDER BY JOKE_NO'' EXEC ( 'SELECT * FROM OPENQUERY(lnk_joke__cat,' + @sSQL + ')' ) END
My Questions: 1). Is there any problem in SP as I am using OpenQuery? I queries the SP and concluded that it generates result properly.
2). Is there any problem with the Recordset.MoveLast line? I am using adOpenKeyset, adLockReadOnly as parameters to my Recordset.Open command along with other parameters.
Let me know the corrective steps to be taken to get rid of this error.
Thanks in Advance for your valuable time Ranjan Jain
how to generate date backward from end to start like this begin -- loop to insert date backward while @end_date>=@start_Date begin INSERT INTO @tb_temp
from middle of the month to end of the month
serial date ------------------------------ 1 19/03/2008 2 18/03/2008 3 17/03/2007 .............. 19 01/03/2007
and put it in this part of code tnx
Code BlockDECLARE
List_of_emp CURSOR FOR
SELECT
emp.empId,emp.ShiftType,emp.StartDate,emp.EndDate FROM @empList emp
OPEN
List_of_emp
FETCH
List_of_emp INTO @input_empID , @last_shift_id ,@StartDate,@EndDate
SET @current = @StartDate
-----------------
-- loop on all in the list
while
@@Fetch_Status = 0
begin
-- loop to insert info of emp shifts
while
@current<=@EndDate
begin
INSERT INTO @empShifts ([empID],[ShiftDate],[ShiftType],[StartDate] ,[EndDate])
I'm relatively new to SQL Server. I have spent some time in Enterprise Manager for our SQL Server 2000 instances. We are testing SQL Server 2005, and I found that I was able to register 2000 databases into the new SQL Server 2005 Management Studio.
Code Snippet SELECT empID, unit_date, unit, ISNULL(NULLIF ((unit + DATEDIFF(mm, unit_date, GETDATE())) % 4, 0), 4) AS new_unit FROM dbo.empList
i have this code this code change the value field "new_unit" evry month from 1 > 2 > 3 > 4 like this evry 4 month it return to 1 >2.......... ------------------------------------------
if i put unit_date = 01/05/2008 and unit=1 than new_unit=1 IT OK
but
if i put unit_date = 01/04/2008 and unit=1 than i get new_unit=2
but it should be 3 it dont go backward ok
if i put unit_date = 01/06/2008 and unit=1 than i get new_unit=4
I have used SSRS since the original SQL 2000 beta, so am pretty experienced with it.
I think there may be a bug in V2.0 (2005) that did not exist in V1.0:
Have just started cutting over my V1.0 reports to V2.0 (2005). One of my users today showed me that the "Find" feature within a V2.0 report searches forward fine. In one case, a three page report, it found the first item on the third page. However, when the "Find" feature was used from that point to get something on the first page, a message was received that it could not find the item. After manually navigating back to page one, and re-entering the same data in "Find" from there, it found the data with no problem on page one.
Can any one give me brief useful explanations or guide me to a usefulresource of what Development Tools component and Profiler are?Is there anything I should be aware of if I want to install ClientConnectivity component (don't want to overwrite anything)?Thank you in advance.
We have our custom install code using C# for a huge Client desktop application. We package SQL Express 2005 along with Backward Compatibility pack as this application was using MSDE before and at 11th hour management decided to pack SQL Express and backward compatibility pack.
During installation we want to detect if the Backward compatibility pack is already installed to avoid overwrite. Can anyone suggest how to detect if Backward compatibility pack is already installed using C#? I am sure there should be some registery keys to look for but don't know which.
I have been trying to create, then call an activeX object. I use sp_OAcreate and then sp_OAmethod to create the object, the call the method within. I have registered the DLL but I can not get it to work. I used the examples within T-SQL help but it doesn't seem to work. I am calling from within a sp within the northwind db. I need to pass 4 parms to the method. Here is the proc.
CREATE PROCEDURE SIMPLE2_SP (@CUSTOMERID nVARCHAR(25) = NULL, @ORDERID INT = NULL) AS
DECLARE @BLOB nVARCHAR(1200), @PARM1 nVARCHAR(25), @SF INT, @pOBJ INT
/***Make sure that the customerid is specified, if not, get out. sfogli 7-17-00 ***/ IF (@CUSTOMERID is NULL) OR (@CUSTOMERID = '') BEGIN RAISERROR('Must specify a CUSTOMER name.',-1,-1) RETURN (1) END
/***Hardcode the path, customerid, and orderid for testing purposes. sfogli 7-17-00. ***/ --SELECT @BLOB = 'PATH=C:REPORT.HTM;CUSTOMERID=' + @CUSTOMERID + ';' + 'ORDERID=' + CONVERT(VARCHAR(5),@ORDERID)+ ';' SELECT@PARM1 = 'PATH=C:REPORT.HTM;'
/***Make sure that the orderid is specified, if not, raise message. sfogli 7-17-00 ***/ IF (@ORDERID is NULL) OR (@ORDERID = '') BEGIN RAISERROR('To continue process, please specify an ORDERID and retry.',-1,-1) PRINT @BLOB RETURN (1) END
I have a Windows XP machine that I have run SQL Server on in the past.I recently re-formatted the hard drive and re-installed XP from scratch,and now when I try to re-install SQL Server 2000, I get an error messagesaying that the "server component is not supported on this operatingsystem. Only client components will be available for installation." Ihave a hard time understanding why the server components can't beinstalled on XP, especially since I've installed them before on thissame machine.Can anyone explain why this might be, and what I can do (if anything) sothat it can be installed again?Thanks.Steve
Question I have Reporting Services up running in production. I want to create a place for internal employee's to go run report only related to daily business. Meaning I want two Sever Components to deploy reports to one for production (Customers) and one for internal(Intranet). Can this be done?
Can someone direct me to step by step intructions?
