November 6, 2009 at 2:47 am
Hi,
I am running SQL 2005 64-bit on a server. On that server we have the engine, analysis services and reporting services running on v3215 (SP2 CU5). SSIS is running 3042 (SP2). Management Studio version is 3042 and the Native client is 3042.
My local machine I use to administer is a 32bit Management Studio running 3042 (sp2).
Having different versions everywhere - is this an issue?
November 8, 2009 at 1:57 pm
Anyone?
November 8, 2009 at 4:23 pm
Shark Energy (11/6/2009)
Hi,I am running SQL 2005 64-bit on a server. On that server we have the engine, analysis services and reporting services running on v3215 (SP2 CU5). SSIS is running 3042 (SP2). Management Studio version is 3042 and the Native client is 3042.
My local machine I use to administer is a 32bit Management Studio running 3042 (sp2).
Having different versions everywhere - is this an issue?
I am not aware of any issues with using x86 which is 32bits to connect to x64 because most companies run x64 server and developers run x86 to connect to it. You can also write code in x86 and deploy in x64, you should know if the code is CLR you will need to build the code AnyCPU instead of x86 because if you build x86 and deploy in x64 you will get an exception. That is not related to SQL Server and BIDS development.
Kind regards,
Gift Peddie
November 8, 2009 at 7:15 pm
Have you experienced problems ? or you're just curious ?
I have 32 bit everywhere except for 1 VM server running Windows 64 and SQL 64. No issues, although it's a lightly used test machine so it's not stressed much.
November 9, 2009 at 2:48 am
We do have some issues here and there with this server but it is probably down to performance tuning (mentioned in other posts).
November 9, 2009 at 5:49 am
It is not in itself wrong to have different fix levels for different components of SQL Server. If a new CU is issued and it contains no fixes for (say) SSIS but does contain fixes for SSAS, then the fix level of SSIS will not be changed after applying the CU, but SSAS will have a new higher fix level. This concept is standard across just about every software product on the market.
The important thing is to know if all the maintenance you think you have applied actually was applied.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply