I have an SSIS job that is exiting with an error on a 64 bit Itanium SQL 2005 sp1. It has three parallel streams of execution. I've been running my tests using dtexec with verbose output being sent to a file.
2 of the streams execute several truncates and then are followed by 4 steps that load data from a SQL 2000 server to a SQL 2005 server. One of the job streams sources it's data using a SQL Server username/password while the other sources it's data using integrated security. Both streams use integrated security for the destinations.
The third job truncates 2 tables and then loads those two tables from an Oracle database. The oracle connections use a username/password in a connection string in a configuration database while the SQL side of the connection uses integrated security.
I've validated security is working, I've validated the drivers for Oracle are working in 64 bit mode and 32 bit mode for the connection strings I'm using, and security for the package. To top it off, this package runs to completion in 32bit mode under the same credentials.
The only warning messages I get running in verbose mode are the following warnings from the Oracle connection:
OnWarning,311-SQL-01,CHARLOTTE!lcharlton,Import Employee Locator,{EE2C1DB7-A767-4AE6-81F4-6FAE6BFBD2CF},{DF323107-1ABD-4790-A318-B046862C6F58},10/19/2006 2:24:55 PM,10/19/2006 2:24:55 PM,-2145378202,0x,Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.
Any insights into how to troubleshoot this or possible additional steps I could take are warmly welcomed.
We have a 64bit installation of SQL Server (SSIS, SSAS) running and working fine. There is a requirement to install 64bit SSRS on this existing setup. The problem is: While running the SQL Server Setup wizard, the Reporting Services checkbox remains greyed out. In other words, there isnt an option to select SSRS for installation. So the question is: Is it even possible to install 64bit SSRS on an existing 64bit SQL server installation - given that SSRS wasnt installed during the first pass. PS: The SQL Server is SP2 on a Windows Server 2003 configured as an App Server.
I just installed the 64bit Vista and than wanted to install the 64bit SQL 2005 Std. Server on it.
Note: I downloaded my license from https://licensing.microsoft.com/eLicense/L1033/ProductDetail.Asp?SKU=228-05338.
Installing from SQLSTDSEL.ISO file results in the warning that for the REPORT- Server the .NET version has to be 32bit.
Stopping the installation at this point and try to install from SW CD SQL Svr Standard Edtn 2005 64Bit X64 English #1 x64 MLF.x11-57664 + SW CD SQL Svr Standard Edtn 2005 64Bit X64 English #2 x64 MLF.x11-57665 does not give the above error but on the other hand installs no server at all since somehow the installation routine is not working at all.
Installing now - after at least analysis server and reports server are 64bit and installed - from the first mentioned ISO results in the installation of the DB- Server.... but as a 32bit installation.
Now I wonder what did not work out - so maybe someone here has an idea if and how this problem is solveable.
how can someone build user defined functions and procedures in c# using Microsoft Visual Studio 2005 Professional Edition (SP1) and compile them for the IA64 platform (Itanium)? There is no target platform option "Itanium" in the project's properties (in the Build tab).
I am replacing a production database. Initially I sized a Quad 2.8GHz with 8 GB of Ram. I will be running Windows 2003 EnterpriseServer with Sql Server 2000 Enterprise. I was wondering what kind ofperformance I would (better/worse) get from a Dual 1.5 GHz Itaniumwith 8 GB of Ram running the 64 bit versions of Windows 2003 and SqlServer. Hardware cost are pretty comparable, but I could save on SqlServer licenses. Anyone that has some experience or has anydocumentation that could compare the amount of processing powerbetween the two architectures. Example: A 1.5 Itanium is comparableto 2 2.4 Zeons. Any help would be appreciated.
We need to pull data from our DB2 system to our Itanium SQL Server.
Is this simply a matter of setting up the 64-bit DB2 Connect drivers on the Itanium box with the exact same DSN name used on ther 32-bit box used to define and deploy the SSIS package?
Has any one done this, yet? If so, is there anything that we need to look our for?
While SQL Server installed into our clustered environment with no significant problems Service Pack 2 will not install with the Error "Unable to install Windows Installer MSP file" during the update to the Database Services.
Subsequently, Integration Services, Native Client and Backwards Compatibilty also fail to upgrade due to suspended installs.
Searching for this returns a number of articles none of which match what we are seeing, including:-
http://support.microsoft.com/kb/918357 indicates this is a problem with the Setup Support Files. This is not the case and the Setup Support files are updated. Also the permissions are correct on the folder and files mentioned,
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=448685&SiteID=1 also point to a problem when installing the Setup Support Files. Our install gets past this but fails on the database engine then sets up a chain of suspended installs.
Other finds indicate there may be another msi running, again this is not the case and the server has been failed over and rebooted a number of times.
At the moment we are sitting at RTM having rebuilt the machine completely but would like to move forward onto SP2. Has anyone come across this and provide any further information or resolution?
We have successfully deployed SP2 onto a number of other servers cover both clustered and non clustered, 32 bit and X64 installations with no problems and now wondering if the problem is Itanium edition specific.
extract from the install log from the failed install. The logs mentioned in this log do not exist post install, in fact the Hotfix folder is not there.
Prerequisites Check & Status SQLSupport: Passed ********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.00.1399.06 IA64 Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 IA64 ENTERPRISE Integration Services ENU RTM 9.00.1399.00 IA64 ENTERPRISE SQL Server Native Client ENU 9.00.1399.06 IA64 Client Components ENU RTM 9.00.1399.06 IA64 ENTERPRISE MSXML 6.0 Parser ENU 6.00.3883.8 IA64 SQLXML4 ENU 9.00.1399.06 IA64 Backward Compatibility ENU 8.05.1054 IA64 Microsoft SQL Server VSS Writer ENU 9.00.1399.06 IA64 ********************************************************************************** Products Disqualified & Reason Product Reason ********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID ********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 1399 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 1601 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log Error Number : 1601 Error Description : MSP Error: 1704 An installation for Microsoft SQL Server 2005 (64-bit) is currently suspended. You must undo the changes made by that installation to continue. Do you want to undo those changes?
I'm having an odd issue trying to run an SSIS package on a 64 Bit SQL 2005 SP2 (build 3042) Windows 2003 SP2 64 bit AMD Cluster. I have to use the dtexec cmd line utility from SQL Server Agent because I need to connect to an Access database. When running the package from dtexec, it doesn't seem to be able to load the package, i keep getting this error:
Executed as user: USSI-CORPsql02admin. ...00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:56:00 PM Error: 2008-03-03 13:56:01.28 Code: 0xC0010018 Source: {DFBF51D9-DF81-41B9-9370-9DFC68E28FBA} Description: Error loading value "<DTSropertyExpression xmlnsTS="www.microsoft.com/SqlServer/Dts" DTS:Name="Subject">@[User::vString]</DTSropertyExpression>" from node "DTSropertyExpression". End Error Error: 2008-03-03 13:56:01.28 Code: 0xC0010018 Source: {DFBF51D9-DF81-41B9-9370-9DFC68E28FBA} Description: Error loading a task. The contact information for the task is "Send Mail Task; Microsoft Corporation; Microsoft SQL Server v9; ? 2004 Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1". This happens when loading a task fails. End Error Error: 2008-03-03 13:56:01.53 Code: 0xC001000E Source: TestMsgBox Description: The connection... Process Exit Code 1. The step failed.
The @[User::vString is a string variable in the package, and this particular package is actually just using the SendMail task without using an Access DB, as i'm trying to just get the dtexec utility to work. I believe i'm either doing something wrong or have found a bug, as i've used this in the past at another company without any issue.
Here's the cmd line that I'm using (I'm using the 32 bit version of dtexec): E:Progra~1Micros~190DTSBinndtexec.exe /SQL "TestMsgBox" /SERVER D1PSQL02V /CHECKPOINTING OFF /REPORTING EW
I have many problem when I try to install SQL 2005 Ets edition ia64 on a 2003 ets Itanium edition.
When I launch the setup, all is all right. But during the installation, it tryes to start MSSQL services.
The staring of this service failed. So I try to start the service mannually. Nothing.
Error messages I can get (in the event log) :
Source : Service Control Manager ; ID : 7000
Description :Service SQL Server (MSSQLSERVER) failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Source : MsiInstaller ; ID 10005
Description : Product: Microsoft SQL Server 2005 (64 bits) -- Error 29503. Failure of the starting of service SQL Server. For more information, to see the headings of on line help €śProcedure: to post the files newspapers of installation of SQL Server 2005€? and €śmanual Starting of SQL Server€?. This error is (1053) The service did not respond to the start or control request in a timely fashion.
Hi, we work with the Reporting Services of the Itanium Edition of SQL Server 2005. With some reports (only some) we have the problem that very long time is needed for the processing of the report. I checked the ExecutionLog table in my Reportserver database and detected that values in the column TimeDataRetrieval (TDR) or pretty slow, but them in the column TimeProcessing (TP) are very high. Report1: TDR = 8304ms TP = 34377ms . In other (most) reports the values are completely different Report2: TDR 8336ms TP = 233ms
Now the most interesting thing: When I execute the same report on our test server which is a xeon machine (same data volume, no user workload) I get the following results: Report1: TDR = 5244ms TP = 11731ms Report2: TDR = 4750ms TP = 163 The differences in TimeDataRetrieval (TDR) should be ok, because the machine is used by over 700 people and so the response times of the Analysis Server database could differ. Report1 and 2 do not differ too much in complexity. A few groupings, parameters and so on.
The Itanium machine is a 2 way dual core system with 16 Gigabyte RAM. The Xeon machine is a 2 way xeon system with 8 Gigabyte RAM (32bit processors).
What is going on there? How could I optimize the TimeProcessing of Report1 on the Itanium machine? Which performance counters or tools should I use to go deeper finding out where the problem is?
I am working on a project to write SSIS packages to update a SQL Server 2005 database with data from an Oracle 10g database. Unfortunately, our development ETL box is running 32 bit Windows Server 2003 while the production ETL box is running 64 bit Itanium Windows Server 2003. We have created SQL Server Agent jobs to execute all of our packages. All of our jobs run without error on the 32 bit development box, but in our preproduction tests they are failing in the 64 bit box.
In my testing, I've found that I can successfully pull character data from Oracle. For example, I can write a package that retrieves the data for the following query:
SELECT 'test' FROM dual
However, the following fails:
SELECT 1 FROM dual
I have logging turned on in my package. When the package fails, I typically see informational messages in the log up to the point of failure, but no actual error event logs are generated. The only error information I have is in the SQL Server Agent job history log, which contains the following:
Executed as user: SERVERNAMESYSTEM. The return value was unknown. The process exit code was -2147483646. The step failed.
I have also tried using the 64 bit version of the DTS Wizard to create a sample package, and observe the same behavior. When I run the DTS Wizard, queries that return numeric data cause DTSWizard.exe to exit and produce the following message in the application event log:
Event Type: Error Event Source: .NET Runtime 2.0 Error Reporting Event Category: None Event ID: 1000 Date: 2/1/2007 Time: 12:36:13 PM User: N/A Computer: SERVERNAME Description: Faulting application dtswizard.exe, version 9.0.2047.0, stamp 443f5e50, faulting module oracore10.dll, version 10.2.0.1, stamp 435841b0, debug? 0, fault address 0x00000000001e4910.Has anyone else experienced similar behavior, and know of a solution aside of wrapping all retrieval of numeric data in to_chars in our Oracle queries?
I recently updated the datatype of a sproc parameter from bit to tinyint. When I executed the sproc with the updated parameters the sproc appeared to succeed and returned "1 row(s) affected" in the console. However, the update triggered by the sproc did not actually work.
The table column was a bit which only allows 0 or 1 and the sproc was passing a value of 2 so the table was rejecting this value. However, the sproc did not return an error and appeared to return success. So is there a way to configure the database or sproc to return an error message when this type of error occurs?
I have a parent package that calls child packages inside a For Each container. When I debug/run the parent package (from VS), I get the following error message: Warning: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
It appears to be failing while executing the child package. However, the logs (via the "progress" tab) for both the parent package and the child package show no errors other than the one listed above (and that shows in the parent package log). The child package appears to validate completely without error (all components are green and no error messages in the log). I turned on SSIS logging to a text file and see nothing in there either.
If I bump up the MaximumErrorCount in the parent package and in the Execute Package Task that calls the child package to 4 (to go one above the error count indicated in the message above), the whole thing executes sucessfully. I don't want to leave the Max Error Count set like this. Is there something I am missing? For example are there errors that do not get logged by default? I get some warnings, do a certain number of warnings equal an error?
Starwin writes "when i execute DBCC CHECKDB, DBCC CHECKCATALOG I reveived the following error. how to solve it?
Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -2093955965, index ID 711, page ID (3:2530). The PageId in the page header = (34443:343146507). . . . . . . . .
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1635188736)' (object ID -1635188736). CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1600811521)' (object ID -1600811521).
. . . . . . . .
Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -8748568, index ID 50307, page ID (3:2497). The PageId in the page header = (26707:762626875). Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -7615284, index ID 35836, page ID (3:2534). The PageId in the page heade"
I have an SQL2005 db residing on a 64bit server.I can load and run my App, provided it is installed on the server.However when I try to run from a Client's PC I get timeout errors.
Initially the error was Remote connections not allowed,but I have overcome this by ensuring SQLbrowser was running and that AllClient and Server Prodtocols were enabled.
I now keep getting a message the timeout has expired.
please tell me what is 32 bit and what is 64 bit databases in sql server? is that based on versions line 7.0 , sql server 2000, yukon and katmai like that or based on creation? please explain me
thank you very much
Vinod Even you learn 1%, Learn it with 100% confidence.
I run SQL Server 2005 on a Windows 2003 64-bit server. I have created a package where I run an execute t-sql statement task. In the t-sql I have the following:
select * from OpenDataSource('Microsoft.Jet.OLEDB.4.0','Data Source="c: est.mdb";User ID=Admin;Password=').pubs.dbo.data
and I get the following error:
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
We have an ASP 2.0 application built using SQL Server 2005, on a 32 bit system. We are going to bring in a much faster server and move the applicatioin to the new server. Since we are moving to a faster server, we are also considering putting a 64bit version of SQL on the new machine and running as 64 bit.
Now the rookie questions: 1) If we do this do we need to do anthing special with our procs/functions, i.e. do we need to recompile everything? 2) From an asp perspective, do we need to do anything to our pages/code? 3) what other issues do we need to be cognizant of?
Hey guy's I am trying to develop something on a 64bit Vista machine. However, the SQL server 2005 import wizard is having a tough time importing my data because this machine does not have IIS.
I tried to install the regular version and it would not let me based on my system.
I'm sure this has been discussed in the forums before, but I'll ask anyways. I'm replacing our GP server next year to one that will run SQL2k5 64-bit. The current server is only capable of 32bit SQL. I know with some databases changing from x64 to x32 is a bad idea...will SQL Server support it?
I have found that orig tested 64 bit on our 64bit windows 2003server...about 1 year ago...and company decided to use sql 32 bit on the64bit osmy question and any information is very welcomeis there any things in need to know about awe withmemory above 4g ...whilst using 32 bit sql on a 64bit osi want to increase the memory on the server buti really don't know what im up against since this ismixed system 32 bit sql and 64 bit osthanksmike
We have a sql2005 server, wich have 10 databases mirrored. Yesterday we had the following error:
Date 21-08-2007 14:13:18
Log SQL Server (Current - 22-08-2007 13:00:00)
Source Server
Message
Resource Monitor (0x2d18) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 88080 KB. Approx CPU Used: kernel 234 ms, user 109 ms, Interval: 60000.
The error cause that one of our databases generated an automatic failover.
Hello all, I'm going to be upgrading our server hardware that runs SQL2000std, and would like to move to a 64bit windows server 2003 on a 64bit server. Right now we running it on a windows 20003 server. with what I read I think I can run SQL2000 std. w/SP4 on a windows 2003 64bit server but would like some one to confirm that for me.
Having looked at the complexities of transforming data from Oracle in a 64Bit Environment to SQL 2005, will SSIS 2008 run nativley in 64Bit. I understand that SSIS 2005 ran in 32Bit, even when in a 64Bit environment, causing great issues in accessing Oracle. Oracle released an update to compensate for this, however can someone please clarify whether SQL 2008 will have the same issues, or will SSIS 2008 be able to speak with Oracle on a 64Bit level. Regards
I have SQL 2005 Enterprise 64bit SP2 on windows 2003 EE 64bit SP2 w/24gig memory. My problem is that it wont use more than 110mb of memory according to task manager processes and performance. I've tried messing with the min and max and rebooting each time I make the change and sill nothing. Currently Ive changed it back to default. The server shows up as 24gig so it is seeing the memory. Any ideas? I thought 64bit was supposed to be better about this kind of thing.
Also, AWE has always been unchecked as this is a 64bit box.
