I am going to test the migration of a 32bit SQL 2005 database to a SQL 2005 x64bit database server. Has anyone tried this? What can I expect? Will it work? Is there anythi I need to do?
I was just going to detach the 32bit DB, copy yhe files to the 64 bit server and reattach it.
Thanks
Hi ,
I am trying to link with Linked server to MDB file, when i try to create the linked server i i cant find the Jet Ole db provider, how i can link it ?
This may seem like a completely foolish question, but is there any issue in using the 32bit workstation components (on XP) to connect to the 64bit server-side components? New to SQL2K5 and never had any issues using the 2K workstation/server components together.
Thank you!
issue:
i have an ASP-Application running fine with both SQL Server 2000 and SQL 2005 (both 32 bit)
Now i have to attach a 64bit SQL-Server.
I have a problem with the connection:
This one runs fine with sql 2005 32bit
<%set myConn = Server.CreateObject("ADODB.Connection")
myConn.open "driver={SQL Native Client};server=<servername>;database=<dbname>;uid=<uid>;pwd=<pwd>" %>
but not with the 64-bit server:
ADODB.COnnection error "800a0ea9". Provider is not specified and there is no standard provider.
ok, i did some research and came up with the following:
<%set myConn = Server.CreateObject("ADODB.Connection")
myConn.open "PROVIDER=SQLOLEDB;DATA SOURCE=<serverip>,<serverport>;database=<dbname>;uid=<uid>;pwd=<pwd>" %>
thats fine, now i get a connect.
Unfortunately, this provider seems to behave different to the one i use in 32bit :
Lets say i have a stored procedure"
create spName as
select * from mytable
when i execute the following
<%sqlstr = "exec spname"
set myRecSet = CreateObject("ADODB.Recordset")
myRecSet.open SQLStr, myConn
response.write(myRecSet(0)) %>
it gives the first value of the first row with the Connection to a 32bit SQL-Server
but myRecSet seems to be empty on my 64bit SQL Server the response.write leads to an error message.
As far as i understand this, the provider used when connecting to a 32bit Server returns the records selected by the last row of the stored procedure into the recordset, but the provider when connecting to a 64bit server does not return these results.
What can i do, if i dont want to rewrite my asp-programming. I hope somebody has the correct naming / syntax for an connection string which allows me to connect my asp-application to the 64bit SQLServer which behaves like the "old" one for 32bit.
I hope my comments are clear enough - english is obviously not my mother-tongue - and somebody can give me a hint.
Thanks,
Heinrich
I installed SQL 2005 on a 64bit server. Can I still use enterprise studio on a 32bit client machine?
The install CD's are 64bit and when I try to find the enterprise studio to install on my 32bit machine i get an error. Is there a place to download the 32bit enterprise studio? What are my options here?
Thanks in advance.
Mike
Hello,
Are there any issues with running the 32 bit version of Windows 2003 server and SQL Server Standard edition on a 64 bit Intel hardware Platform? I don't see why there would be if the OS is 32bit but just thought I'd ask.
Thanks.
I have two 64bit SQL Server Std servers that will be principal and mirror. I also need to stand up a witness. I already understand that the witness can be any version of SQL Server, but can the witness server be 32bit given the principal and mirror are 64bit?
Hi,
Recently, we have migrated our database from 32bit to 64bit. So far the application is working fine.
But I want to confirm that by any tool or automated process.
Is there any way or tool to check that the migrated data is correct and also to check if migrated database objects will work fine in 64 bit environment.
Any timely help would be greatly appreciated !!
Thanks,
Bala
Hi, All:
We have to migrate several 64Bit SQL Servers to 32Bit platform. Due to the 64Bit source systems are all production system, the downtime is too limited. So we can only get the DB files via Detach way. Among the source systems, both SQL2000 and SQL2005 exist.
My question are:
Is it possible to migrate the DB from 64Bit to 32Bit via Detach/Attach?
If ok, how to do that?
Any info will be highly appreciated! Thanks!
Best Regards,
Kevin
Hello,
How can I link server to a 32bit ORACLE from a 64bit MSSQL?
LiJun
I am about to work on a SQL server 2005 migration and I have no clue what SQL server 2005 is as I have been working on 2K all along.
Fist of all I am not sure if the given box is having 64bit or 32 bit Operationg System?
Second of all I am trying to find if the SQL server 2005 installed on this box is 32bit or 64bit?
Thanks in advance,
sk
I have a package that I developed in VS2012 (using the SQL Data Tools component) which collects data from a DBF file using the VFPOLEDB provider, and puts it into a database on a SQL Server 2012 X64 server. The project containing the package has the DebugOption of Run64BitRuntime set to false. I have imported this package to the SSIS Package Store of a test and live server (identical setups). The VFPOLEDB provider is installed on both, and I can see in the registry of both machines that it's there for 32bit runtimes.
The package runs fine on the test machine, but fails on the live machine. The live instance of SQL does not appear to recognize the 32bit VFPOLEDB provider that is installed.The only difference in the instances of SQL is that the live environment has an Integration Service Catalog set up, where as the test does not. Looking at the logs of the servers, when the live starts, it runs sp_ssis_startup, and then logs messages about unsafe assemblies being loaded in. This SP is not run on the test environment because there is no catalog.
The jobs I create have the flag set to use the 32bit runtime, but I feel that the SSIS Catalog is having an issue with the VFPOLEDB I am using, and not loading it.
We have recently migrated from SQL 2000 (32bit) to SQL 2005 on Win2003 (both are 64bit). And we have Legacy DTS packages on SQL 2005, some packages are pulling records from Oracle 10g (32bit server). When I execute the DTS package I am getting following error.
Error = -2147467259 (80004005) Error string: Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation. Provider is unable to function until these components are installed. Error source: Microsoft OLE DB Provider for Oracle
Did I need to install/update any MS OLE DB driver for Orace.
Some blogs & forums suggesting to install Oracle 10g Client. If so Which version of Oracle client(32bit/64bit) I have to install?.
Thanks.
Dhans
I installed what I thought was SQL Server 2005 64bit, but I'm not sure. I used my action pack Microsoft SQL Server 2005 CD, and it's on a Windows 2003 64 bit machine. When I click help -> about in the SQL Server Management Console, it says "Microsoft SQL Server 2005". There's no 64 bit in there.
Can someone tell me how I can find out if I've correctly installed the 64 bit version?
Thanks.
Chris.
I have designed a packege using my local machine ( 32bit) and am trying to deploy this package to 64bit machine and open it up.. are there any issues that I need to aware of? 32 bit ssis and 64bit ssis are comparable each other?
View 14 Replies View RelatedDear,
I have application create by MsAccess
and connect with Sql Server 2000 in x86
and now we transfer system to
HP rx3600 Intel Itanium
- Install Windows 2003 Server Enterprise (for Itanium)
- Install Sql Server 2005 Standard Edition (IA64)
and now we try to create ODBC connection
from client for testing.
But we can't not done it.
Anybody can tell us
how to create connection to sqlserver 2005 (ia64)
Regards,
Tee+
I am attempting to install SQL Server 2005 on a Laptop with Windows 2003 Standard Edition.
The installation fails and the File Summary.txt has the following entries:
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Fri Nov 30 09:36:53 2007
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_BOL_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLXML4_1.log
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Fri Nov 30 09:38:41 2007
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_BOL_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLXML4_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SCC.log
The Log File, SQLSetup0004_<hostname>_Core.log, has the following entries:
Microsoft SQL Server 2005 Setup beginning at Mon Dec 03 08:54:09 2007
Process ID : 2980
C:SAP_CDCD2x86EnterpriseEditionServerssetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/11/3 8:54:9
Complete: LoadResourcesAction at: 2007/11/3 8:54:9, returned true
Running: ParseBootstrapOptionsAction at: 2007/11/3 8:54:9
Loaded DLL:C:SAP_CDCD2x86EnterpriseEditionServersxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/11/3 8:54:9, returned true
Running: ValidateWinNTAction at: 2007/11/3 8:54:9
Complete: ValidateWinNTAction at: 2007/11/3 8:54:9, returned true
Running: ValidateMinOSAction at: 2007/11/3 8:54:9
Complete: ValidateMinOSAction at: 2007/11/3 8:54:9, returned true
Running: PerformSCCAction at: 2007/11/3 8:54:9
Complete: PerformSCCAction at: 2007/11/3 8:54:9, returned true
Running: ActivateLoggingAction at: 2007/11/3 8:54:9
Complete: ActivateLoggingAction at: 2007/11/3 8:54:9, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2980" returned false.
Running: PerformSCCAction2 at: 2007/11/3 8:54:9
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042
Complete: PerformSCCAction2 at: 2007/11/3 8:54:9, returned true
Running: PerformDotNetCheck at: 2007/11/3 8:54:9
Complete: PerformDotNetCheck at: 2007/11/3 8:54:9, returned true
Running: ComponentUpdateAction at: 2007/11/3 8:54:9
Complete: ComponentUpdateAction at: 2007/11/3 8:55:6, returned true
Running: DetectLocalBootstrapAction at: 2007/11/3 8:55:6
Complete: DetectLocalBootstrapAction at: 2007/11/3 8:55:6, returned true
Running: LaunchLocalBootstrapAction at: 2007/11/3 8:55:6
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1605
Aborting queue processing as nested installer has completed
Message pump returning: 1605
Regards
We recently migrated our 32bit instance of SQL Server 2005 SP2 to a 64bit instance of SQL Server 2005 SP2. The migration was performed by copying all .mdf and .ldf files (including master, tempdb, etc...).
Everything seems to have worked nearly flawlessly except for a few glitches seeming to relate to the master database. I am hoping there is a way to mitigate these issues without reinstalling and performing the migration again.
First, when attempting to view the Activity Monitork, I get the error:
TITLE: Microsoft SQL Server Management Studio
Cannot show requested dialog.
Unable to execute requested command.
Unable to launch Activity Monitor. You may not have sufficient permissions. (ActivityMonitor)
View or function 'master.sys.dm_exec_sessions' has more column names specified than columns defined. (Microsoft SQL Server, Error: 4502)
Second, the procedure: master.dbo.sp_procedure_params_rowset fails because of the line: option (OPTIMIZE CORRELATED UNION ALL).
Like I said, I know this is probably an issue arising from copying the master database, but if it is at all possible to avoid another migration, I want to.
Mike Thomas
Software Developer
The Master's College
We have a 64bit os machine that we accidently loaded the 32 bit version of sql server on. We now want to upgrade it to 64 bit sql server, but we now have a production database on it. My understanding is that all I have to do is detach the production database, upgrade to 64bit sql server, then reattach the database. Is this really all I have to do?
View 4 Replies View RelatedI'm very new to SQL servers. We're running SQL 6.5-SP4 and have three applications using different databases on the server (NT4-SP3).
App 1. Written in PowerBuilder using 32bit DB_LIB, NWLink IPX/SPX.
App 2. Written in VFP 5.0a using ODBC32, NWLink IPX/SPX
App 3. Written in VB using ODBC16, NWLink IPX/SPX
Something happens, which freezes all 32bit connections and prevents any other 32bit connects. Which means I can't get Enterprise Manager to connect! This does not affect the ODBC16 clients?!?!
So far the only way, I have found, to clear and fix is to get all 32bit users out of their apps and the server becomes available again. There's got to be something to prevent this, any ideas? Is there a way to trace this to find the culprit?
Thank you for any and all help,
Jim
<jpeppercorn@jhcb.com>
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?
Thanks
Here is a post to the MSDN forums that I have not been able to resolve:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2663783&SiteID=1
Anyone here have any ideas?
I would like to install MS SQL Management Express, and I would like to make sure I am downloading the right files.
Could you tell me how I can find out whether my PC is 32bit or 64bit?
Many thanks
W aka Gauguin
Same server:
Windows 2003 R2 SP2 (32bit)
SQL 2005 SP2
4gigs of Hot-Add RAM
WSUS 3.0 SP1
SCCM 2007
I've had nothing but issues on this server until I came across the articles about using /PAE in the boot.ini to correct the 4gig RAM issues, then read that /PAE can corrupt your database.
I then enabled AWE on the SQL 2005 server using the RAM range of 1gig-4gigs.
Since this, I am seeing errors in the Application Event log on the server that states SQL is not ready to accept client connections.
So, before I go any further with this build, it this something I should be concerned about ?
Thx !
MarcusDOI.gov
Hi All
Can I use Log shipping From 64bit to 32bit in SQL Server2000?
Thanks~
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
Hi all:
advance thanks for ur help..
i need to know what could be the differnet , when use BIGint datatype at 32bit sql2005 and 64bitsql2005??
can i know benefits of bigint if i use at 32bit and 64bit sql2005??
waiting for your valuable reply..
thanks!
Mk..
I m swagatika and working on a s/w company.I am facing some problem in MS SqlServer2005.
my problem is:-
My project is running on SqlServer2005 which is 32 bit support.
But i want to change my project on SqlServer2005 which will be support to 64 bit .
What are the steps i follow to change 32 bit to 64 bit.
can anybody help me?
Just curious if it's possible, and supported, to upgrade SQL 2005 from32bit to 64bit. This is on top of Windows 2003 64bit. Trying to getthe proper supported config for OM2k7 without blowing everything away.Thanks,JDP
View 1 Replies View RelatedWe have jumped straight to 64 bit SQL 2005 with no 32 bit 2005 inbetween.
However this means the tools we have cannot be installed on windows XP/2000 32 bit.
Is there some way to get the 32 bit tools as it appears strange that 32 bit tools were not provided for remote access.
Cheers
Julian
Hi all,
I've got two VLDBs on 64bit hardware platform + 64Bit-W2003K Std R2 + 64Bit SQL2005 Std Edition.
If I set this guy up as the Principal, can I have the standby/member on 32Bit HW + 32Bit W2003 Std + 32Bit SQL2005?
Will this actually work?
Regards,
Uday Shivamurthy
There is no SQL Agent forum so if this isn't the correct place please move this post.
Windows 2003 R2 x64 with SQL Server x64.
One of the steps in a SQL job I have setup requires me to run an exe. I can run this exe from the command line or by double-clicking it on this same server but when running it from a SQL job it does not run, the job just has the status 'executing' but does not do anything. I have enabled xp_cmdshell. I have also tried calling a bat file which then runs the exe and I have tried calling the bat file with SysWOW64cmd.exe. Same problem.
It seems to me the the operating system recognises the 32bit exe and runs it in that context but the SQL Agent thread keeps trying to run it as a 64bit exe and hence never gets anywhere. (My best guess)
Is there a way to force SQL job/steps to run an exe or bat file in a 32bit thread? Any other ideas.
Thanks
Scott
Hi:
I wanted to make sure some things clear before setting up service broker. I have enterprise server as 64 bit and local client servers as 32 bit. I would like to know what steps do I need to take care when I am setting up service broker b/w sql server enterprise editon 2005(64 bit) and sql server express 2005 client server(32 bit)...any special considerations ...?
Thanks,
Pramod