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 ?
I'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?
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.
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?
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 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.
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.
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
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?
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.
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?
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.
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 ...?
Probably a dumb question but our network guy has installed 64 bit Win2003 on one of the servers onto which I'm tasked with running our 32bit SQL Server 2005 server.
The installation goes through without a hitch and I'm able to get the SP2 installed over the top with no problem. I am, however, having trouble when trying to browse into the Reporting Services pages. I simply get a std "Page Not Found" web page. I've gone through the Report Server Configuration to see if I can get things to come up properly and everything appears to be initializing properly but still "no go"...
Can one of you MVP's give me a direction? I know it's relatively few details to get started but I'll provide whatever's necessary to get me pointed in the right direction.
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.
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.
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?
We just built a new server with Windows 2003 64bit OS and installed SQL2005 64bit (named SQLServer let's say) as the default instance and SQL2000 32bit (named SQLServerSQL2000 let's say) as a second instance. The first instance is listening on the 1433 port and the second instance is on the 1344 port.
I can connect to the default instance with Management Studio without issue using the SQL instance name, but to connect to the second instance I have to create an alias with the port number (SQLServerSQL2000,1344) on my machine. I have never had to do that before with a second instance.
I am trying to figure out if this is an issue with 32bit SQL running on 64bit OS or what. I am kind of stumped.
Any information would be greatly appreciated! Thank you!!!
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.
This connection string works for Vista 64bit but not for Vista Business 32bit...
What have I done so far to the Vista Business 32bit... 1. Downloaded/Installed SQLNCLI from Microsoft Site 2. Tested the connection string several ways with no luck... 3. Was able to get Vista Business 32bit to connect via a File DSN with the same credentials... DSN route is not an option for this app...
will not acquire a connection because the package OfflineMode property is TRUE. When the Offline Mode is TRUE, connections cannot be acquired." I'm running the 32bit DTEXEC on a 64bit machine since I'm using the Jet provider. I see in the forum and other places that this error usually occurs when you try to run in 64bit. I don't get this error when I've tried it, running the 64bit DTEXEC or when I run from BIDS on a 32bit machine. Any help appreciated. David
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?
Hi there. I apologize if this topic had already been covered. I'mtrying to find out whether I can load up a data dump files, generatedoff of a 64bit SQL server on Itanium, to a 32bit MSSQL 2K server. Ifanyone has tried this before, please let me know your findings. Thankyou very much in advance folks.j
Just an FYI for those scheduling SSIS packages on 64bit Itaniums. This came to light when using a 32 bit OLEDB driver on a 64bit Itanium.
When manually executing the package on the server through SQL Management Studio, we got the expected results. However, when we scheduled the package as a job, it failed every time. The error was: "The AcquireConnection method call to the connection manager 'ConnectionName' failed with error code 0xC0202009€?.
We tried everything to fix this, but nothing worked. Finally we found that when manually running the package, SQL Management Studio was calling the 32bit version of dtexec.exe, while the Agent calls the 64bit version of dtexec.exe. The fix is to not use the "SQL Server Integration Services Package" type in the job step, but use "Operating system (CmdExec)" type. Then in the command box, call the 32bit (x86) version of dtexec.exe.
I've been having no luck trying to install SQL 2k 32bit on Windows 2003 64bit x86 SP1 - I've found several articles regarding needing to put SP4 on the 64bit OS, but my problem is the SQL 2k 32bit ",,x86setupsetupsql" won't run.
I consistantly receive a "...(localuserdir)Local.ins. Unable to load installaion instructions. Error 703."
And of course, the SP4 setup won't run because there is not an existing SQL Service to upgrade.
