64bit or 32bit?

I want to get SQL Server 2005 for a clinic with 25 user but I am not sure if I should go for the 32bit or 64bit.. what's your recommendation? and why?

You are going to need to provide much more information than that before the question can be answered. However in general if your app is CPU or IO bound moving to 64 bit will not help, if it is memory bound it likely will(but not for sure).|||Clinic with 25 users data can be handled on a 32bit edition without any issues, as recenlty I have had setup of SQL 2005 32 bit on Win2k3 server with 8gb ram etc. without any issues. As referred if the application you are using has any specific requirement for 64 bit then you can consider in this case, it will be better if you are able to explain such requirements.|||

If you are getting new hardware, then I recommend getting 64 bit hardware and 64 bit SQL Server. There will be a longer 'service life' with 64 bit, and you don't know now how your needs will change over the lifecycle.

64-bit ODBC issues with DTEXEC

We've hit a weird problem that we can't resolve. We have a package using ODBC to extract from an AS400. When running the package through DTEXECUI, the package executes successfully. However, it chokes when executing through DTEXEC or as a SQL Agent job on our 64-bit machine. Seems like DTEXECUI is using the 32-bit ODBC driver while DTEXEC and SQL Agent is trying to access an non-existent 64 bit ODBC driver. We're using a DSN-less connection string (Driver={Client Access ODBC Driver (32-bit)};system=AS400;....) so that's not the issue. Anyone else seen this weird error? Any possible workarounds?If the 64-bit ODBC driver is not aviailable, you can run the package in 32-bit mode.

To do this, edit the SSIS step in Agent. Copy the text from Command Line tab. Switch step to use CmdExec subsystem instead of SSIS subsystem. Specify 32-bit DTEXEC as application ("C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" - including quotes) and add the parameters you've copied from Command Line tab.|||Thank you. This will work until we upgrade Client Access to a version supporting 64 bit drivers. This is our first 64-bit server. Was wondering why there was both "C:\Program Files\" and "C:\Program Files (x86)\" directories and didn't know how to execute dtexec in 32-bit mode.

64-bit MSDE?

I've seen references in Microsoft online material to a 64-bit
edition of MSDE - the description of Windows XP 64-bit
Edition Version 2003 refers to it, for example. However,
I haven't been able to find any more information about the
existence, if any, and availability of 64-bit MSDE. I'm
specifically intererested in determining whether it's
available for the server operating system editions .
Can anyone help?
Thanks,
Peter Hornby
Unisys Corporation
Mission Viejo
hi Peter,
"Pete Hornby" <peter.hornby@.unisys.com> ha scritto nel messaggio
news:umltR66KEHA.644@.tk2msftngp13.phx.gbl...
> I've seen references in Microsoft online material to a 64-bit
> edition of MSDE - the description of Windows XP 64-bit
> Edition Version 2003 refers to it, for example. However,
> I haven't been able to find any more information about the
> existence, if any, and availability of 64-bit MSDE. I'm
> specifically intererested in determining whether it's
> available for the server operating system editions .
AFAIK, only the Enterprise Edition is available in the 64bit flavour..
http://www.microsoft.com/sql/evaluat...ew/default.asp and
http://www.microsoft.com/sql/64bit/default.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:c6jga9$cocpm$1@.ID-207518.news.uni-berlin.de...
> hi Peter,
> "Pete Hornby" <peter.hornby@.unisys.com> ha scritto nel messaggio
> news:umltR66KEHA.644@.tk2msftngp13.phx.gbl...
> AFAIK, only the Enterprise Edition is available in the 64bit flavour..
> http://www.microsoft.com/sql/evaluat...ew/default.asp and
> http://www.microsoft.com/sql/64bit/default.asp
Andrea,
Many thanks for your quick response. I accept what you say, but I
remain confused by the statement - admittedly a year old - in
http://www.microsoft.com/windowsxp/6...uation/faq.asp
where the answer to "What's New In Windows XP 64-Bit Edition
Version 2003" includes the line "Microsoft SQL Server Desktop
Engine (MSDE)".
Peter
|||hi Peter,
"Pete Hornby" <peter.hornby@.unisys.com> ha scritto nel messaggio
news:c6jll6$17ca$1@.si05.rsvl.unisys.com...
> Many thanks for your quick response. I accept what you say, but I
> remain confused by the statement - admittedly a year old - in
> http://www.microsoft.com/windowsxp/6...uation/faq.asp
> where the answer to "What's New In Windows XP 64-Bit Edition
> Version 2003" includes the line "Microsoft SQL Server Desktop
> Engine (MSDE)".
as IIS 6.0, I think that MSDE 2000 will be (or is) provided in the 32bit
flavour =:-)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

64bit Mirrored SQL Server Std with 32bit Witness?

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?

Yes the witness can be 32-bit, I use a 32-bit Workgroup Edition witness with 64-bit Enterprise Edition Principal and Mirror.

64-bit linked server to Sybase

Hi,
From my research, it appears that it is not possible to have a linked server
created in SQL Server 2005 x64 use a 32-bit DSN (i.e. created with a 32 bit
driver). The answer is that I need to create a 64-bit DSN in order to
create a linked server in SQL Server 2005 x64. The problem is that many
vendors (i.e. Sybase) do not have a 64-bit driver.
Looks like our migration is SQL Server 2005 x64 will have to wait unless we
can get this to work with perhaps a third party vendore such as Data Direct.
Any one using Data Direct to connect to Sybase from SQL Server 2005 x64?
Thanks,
Rocco M.
(posted in microsoft.public.sqlserver.odbc,
microsoft.public.sqlserver.clients and microsoft.public.sqlserver.connect)Hi,
I've just ran into the same problem linking to Oracle 8i.
MSDAORA, OraOLEDB.Oracle and ODBC drivers do not work.
64 bit drivers have not been released yet... Any workaround except returning
to sqlserver 32bit?
Davide
"Rocco M" <rocco.mastrangelo@.hp.com> ha scritto nel messaggio
news:AHYeg.1209$cY3.584@.news.cpqcorp.net...
> Hi,
> From my research, it appears that it is not possible to have a linked
> server created in SQL Server 2005 x64 use a 32-bit DSN (i.e. created with
> a 32 bit driver). The answer is that I need to create a 64-bit DSN in
> order to create a linked server in SQL Server 2005 x64. The problem is
> that many vendors (i.e. Sybase) do not have a 64-bit driver.
> Looks like our migration is SQL Server 2005 x64 will have to wait unless
> we can get this to work with perhaps a third party vendore such as Data
> Direct. Any one using Data Direct to connect to Sybase from SQL Server
> 2005 x64?
> Thanks,
> Rocco M.
> (posted in microsoft.public.sqlserver.odbc,
> microsoft.public.sqlserver.clients and microsoft.public.sqlserver.connect)
>

64-bit JET drivers or alternative?

Hi all -
I'm enountering the same problem many have previously reported.
Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
Data Flow Task in SSIS where the destination in an Excel spreadsheet
because there is no 64-bit JET driver for Excel.
Is anyone aware of a 64-bit driver now available or any 3rd party
options? Running the entire package in 32-bit mode is not a
possibility, so I can't use the DTExec workaround.
Any assistance would be appreciated --
Jamie > Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
> Data Flow Task in SSIS where the destination in an Excel spreadsheet
> because there is no 64-bit JET driver for Excel.
> Is anyone aware of a 64-bit driver now available or any 3rd party
> options? Running the entire package in 32-bit mode is not a
> possibility, so I can't use the DTExec workaround.
You can vote here:
Microsoft Connect > SQL Server: x64 Jet provider
http://connect.microsoft.com/SQLSer...=12511
7

64-bit JET drivers or alternative?

Hi all -
I'm enountering the same problem many have previously reported.
Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
Data Flow Task in SSIS where the destination in an Excel spreadsheet
because there is no 64-bit JET driver for Excel.
Is anyone aware of a 64-bit driver now available or any 3rd party
options? Running the entire package in 32-bit mode is not a
possibility, so I can't use the DTExec workaround.
Any assistance would be appreciated --
Jamie :)> Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
> Data Flow Task in SSIS where the destination in an Excel spreadsheet
> because there is no 64-bit JET driver for Excel.
> Is anyone aware of a 64-bit driver now available or any 3rd party
> options? Running the entire package in 32-bit mode is not a
> possibility, so I can't use the DTExec workaround.
You can vote here:
Microsoft Connect > SQL Server: x64 Jet provider
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125117