Migrate SQL 2005 to 2008r2 to diferent server running 2008r2

I need to migrate sql server 2005 to a diferent server running windows server 2008r2 and install SQL 2008r2 can some one help with that step by step please
UPDATE:: i just realize its sql 2014 not 2008, does it make it easier or more difficult or same or there is any tool that make it easier?
 thanks for all your response and help.

This is what I follow.
First Run upgrade advisor 2008 r2 against sql 2005 to confim there are no issues,.
Check depreceated features , discontinued functionality, breaking changes etc in sql 2008 r2.
http://msdn.microsoft.com/en-us/library/ms143729(v=sql.105).aspx
http://msdn.microsoft.com/en-us/library/ms144262(v=sql.105).aspx
http://msdn.microsoft.com/en-us/library/ms143179(v=sql.105).aspx
Once this is done, depending upon the criticality of databases I do a performance test on the new server. If doing performance tests then I do all these below steps before hand and do a database refresh during cutover.
So basically take backup of all databases and move it to the new server.
Now need to move the logins using this KB article - <cite class="_Rm">support.microsoft.com/kb/918992 </cite>
Move all jobs/linked servers etc
Setup all the configuration in sp_configure.
Update stats of all the databases + Reindexing of all indexes.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Similar Messages

  • Migrate SQL 2005 from windows 2005 server to Windows 2008 R2 server

    Hi all,
    I need to move our SQL 2005 on a windows 2003 server to a new server with Windows 2008 R2 installed.  Could someone show me what are the necessary steps I need to do?
    Thank you.

    Hey TR,
    As per Microsoft recommendation, Before Installing new server try to run Upgrade Advisor and follow these steps
    1. Take Full backups of all System and Application databases on your 2005 machine.
    2. Script all logins  -- 
    3. Script all jobs 
    4. List out all Maintenance plans and their schedules -- You cant migrate so you have to create them manually
    5. List out all Linked server(s) currently being used.
    6. Check the service pack
    7. Check the Edition
    8. document the existing server settings so that it should match the same (collation,version,...)
    Migration process
    1. Migrate logins
    2. Restore all App databases
    3. Fix the orphan users
    4. create the jobs
    5. create maintenance plans
    6. create Linked Servers 
    7. perform checkdb on all databases
    8. rebuild indexes 
    9. update the statistics 
    10.move all the DTS / SSIS packages 
    11. Point the application to new server 
    12. Testing ....  Change all the application connection string to new server and then start the testing then finally if everything looks good then you can down the sql 2000 server and start using new server.
    LIKE THIS POST, PLEASE VOTE & MARK AS A ANSWER TO HELP OTHERS
    DBA

  • SSRS Reports migration from 2005 to 2008R2

    Hi ..
    I have couple of questions.. looking for answers
    Am new to report migration. We have 1000+ of reports in 2005 which we need to migrate to 2008R2. After googling theweb i got to know that we have an third party utility RSScripter which is used to move the reports from 2005 to 2008.
    Question 1:
    By using the above tool i was able to migrate the reports from 2005 to 2008. However, i am not able to redeploy the reports to sub folder in 2008..
    Example  i have some reports in 2005 at Dev_reports\Reports\.. when i want to copy these reports to Dev_reports\Reports folder they are not moved to sub folder Reports on destination server, but rather they are copied to root folder. Is there any why
    that i can copy the reports to particular folder in destination server.
    Question 2:
    When moved the reports from 2005 to 2008 are all the reports are automatically upgraded and copied to new server(2008)? or we need to explicitly open each and every report in 2008 and deploy to the new report server(2008)?
    And my third requirement is to create couple(2) solution for the above said reports and check in them to TFS as a reporting project.
    one report project with all the reports from 2005 and another with all reports from 2008.
    Appreciate your responses at the earliest. As this is on top priority.. Thanks in Advance
    Sri

    Hi Sri,
    Per my understanding that you are using the RSScripter to move the reports from SSRS 2005 from SSRS 2008 R2, now your first problem is you don't know how to move the reports from the sub folder of 2005 to an specify folder on SSRS 2008 R2, right?
    I have tested on my locak enviroment and can reproduce the issue, by default, when you execute the .cmd file the report will move to the new server's root folder, for example, you have an rdl report in SSRS 2005 which path is "/Test/report1.rdl"
    , when you move to the SSRS 2008 R2 using the tool it will move to the path "home/Test/report1.rdl".
    If you want to move this rdl to the specify folder "home/Test0323/Test/Report1.rdl" you should do the action as below:
    Create the specify folder on the SSRS 2005 but not SSRS 2008 R2, move the subfolder and the rdl in it "/Test/report1.rdl" to the specify folder
    find and check the "/Test0323/Test/Report1.rdl" in the RSScripter:
    the Output will have the path like "Test0323/Test/Report1.rdl",after move to the SSRS 2008 R2, it will also create the path like "/Test0323/Test/Report1.rdl"
    More details information about using the RSScripter tool:
    Migrating SQL Reporting Services to a new server
    For the second question, Generally, reports are not upgraded when you upload a report definition file directly to the report server or SharePoint site. The report is automatically upgraded the first time it is viewed, but the stored report definition file
    remains unchanged. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
    Similar thread:
    If I upload RDL 2005 template on SQL Server
    2014 then will SQL Server 2014 render it without migrating it to 2014 ?
    Details information about upgrade and migration in the below articles for your reference:
    Upgrading Reports
    Upgrade and Migrate Reporting Services
    For the third question please reference to below article:
    TFS Reports using SSRS
    Using TFS2010 with Visual Studio / BIDS 2008 and SQL Server Management Studio
    Regards
    Vicky Liu
    If you have any feedback on our support, please click
    here.
    Vicky Liu
    TechNet Community Support

  • Connect Non-SAP Oracle db (32bit) in sql 2005 (64 bit) using linked server

    Hi,
    I am connecting Oracle 10g database from SQL 2005 using linked server, in which i get the error
    "Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
    OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
    were not found. " (Microsoft SQL Server, Error: 7303)
    SAP Server with sql 2005 db is in 64 bit server / Windows 2003
    Non-SAP Oracle 10g is in 32 bit windows 2003 server.
    i have installed Oracle 64 bit client in the SAP Server and also copied the 64 bit version of dboraslib.dll to the DIR_LIBRARY path. I am able to view the oracle tables in the oracle client.
    But, when i create the linked server, it gives the above error.
    If i install 32 bit version of Oracle client in the SAP Server, i am able to create the linked server in the db level, but, it says "Work Process restarted, session terminated" message in the Z program in SAP.
    The same works in the test environment where both are 32 bit servers. problem is when SAP server is in 64 bit and non sap is in 32 bit.
    Please suggest.
    Thanks and Regards,
    Nagu

    "Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
    OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
    were not found. " (Microsoft SQL Server, Error: 7303)
    check the workprocess traces for errors (and/or SM21). It seems that the system is "not aware" that an Oracle client is installed.
    64bit programs can´t load 32bit libraries/DLLs that´s why the workprocess dumps when you use the 32bit client.
    Markus

  • SQL 2005 x64 poor performance after migration from SQL 2005 x86

    Recently We've migrated SQL 2005 x86 SP1 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3.
    In the work day, there are sometime SQL excpetions like this below. On other hand i can also tell that we already found some queries which has some inner joins and where clauses on nvarchar fileds, because of the nature of application. Such a query
    is running for about 11 seconds on old SQL server, and about 6 minutes on new SQL server. My main question if is this possible just with a change to new architecture of SQL and more last patches and updates for SQL 2005. Is there any way how to get
    this queries running faster, without rewritng them with new ones? Is this also possible this could be also cause for SQL exceptions, which we are facing on SQL server?
    About new hardware, for now we can't find it something wrong. There is basic configuration:
    Cisco UCS  C220 M3S (1U server)
    32GB RAM
    Intel(R)Xeon® CPU [email protected], 6 core
    Disk system: 4xSAS 300GB in RAID5 (OS and DATA) and 2xSATA 1TB in RAID1 (SQL backup)
    RAID controller: LSI MegaRAID SAS 9271-8i (with latest driver and firmware)
    Part of log of dump file:
    2014-05-09 08:30:07.08 spid86      Error: 17311, Severity: 16, State: 1.
    2014-05-09 08:30:07.08 spid86      SQL Server is terminating because of fatal exception c0000264. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling.
    Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
    2014-05-09 08:30:07.08 spid86      Using 'dbghelp.dll' version '4.0.5'
    2014-05-09 08:30:07.08 spid86      **Dump thread - spid = 86, PSS = 0x0000000132A67ED0, EC = 0x0000000132A67EE0
    2014-05-09 08:30:07.08 spid86      ***Stack Dump being sent to D:\MSSQL.1\MSSQL\LOG\SQLDump0087.txt
    2014-05-09 08:30:07.08 spid86      * *******************************************************************************
    2014-05-09 08:30:07.08 spid86      *
    Thanks for any help,
    Matjaž

    >Is there any way how to get this queries running faster, without rewriting them with new ones?
    You need to perform basic performance tuning steps in the new environment.
    Software optimization:
    http://www.sqlusa.com/articles/query-optimization/
    Disk optimization:
    http://www.sqlusa.com/bestpractices/configureharddisk/
    Memory optimization:
    http://www.sqlusa.com/bestpractices/memory-configuration/
    REBUILD INDEXES, eliminate missing indexes & UPDATE STATISTICS.
    If there is still a problem, look in Activity Monitor for expensive queries. Optimize them. As a general rule, you don't want to have expensive queries in RDBMS.
    Kalman Toth Database & OLAP Architect
    SQL Server 2014 Design & Programming
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • SQL Agent job running DTS package running in SQL 2005 is unable to run if job onwer is not logged onto server

    I am currently working on a SQL Server upgrade project for a a client where I am converting old dts packages to SSIS. However for a few of the packages no conversion is allowed to be done. For these few packages I have to use dts legacy components in SQL
    2005 on a windows 2003 server to run them.
    These packages use CAPICOM via an Active X script in the package to envelope connection string data for security within the package. Consequently I have to register the capicom.dll for the job owner (which will execute the job via proxy) and install private
    and public key files via internet explorer. I also do this when I am logged in with my account so i can test the package.
    I have created a SQL Server Agent Job which is used to execute the package. We have a schedule account which is local admin on the server and sysadmin within SQL Server. This account is used to create a credential and then a proxy for the CmdExec subsystem
    is then created based on this credential. A CmdExec job step is then added to the job. The directory of  cmd file which calls the dts package is then entered in the command window.
    Finally a recurring schedule is added to execute the job every 5 minutes. 
    If i am logged in to the server using the scheduled account the schedule runs successfully. I am also able to run the command file manually by double clicking on it. The DTS package is run successfully. However once the schedule is set up and I log off the
    machine and log onto my development machine with my normal account and fire up  SQL Server. I connect to that instance with the schedule and see that the job is failing with and Active X error in the package. From experience with this package this Active
    X  error occurs when the user executing the package has not registered the capicom.dll. This has already been done for the scheduler account because the job runs when the scheduler account is logged in on the server. 
    It almost seems as though the job will only run if the Scheduler account is logged on. If i log directly on to the server with own user account I am able to manually execute the package via the cmd file which indicates that the capciom.dll is registered
    under my account. Yet if I try an run the job in SQL Server when I am logged in under my account (using the scheduler account proxy) then the job fails.
    Does anybody have any idea why this may be happening? Any ideas would be much appreciated

    Run the job SSIS step under a proxy account that is derived from the domain account, non-expiring password and has been set to have all the necessary rights.
    How to is here: http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
    Arthur
    MyBlog
    Twitter

  • Need Checklist for migrating MS SQL 2005 SP2 to MS SQL 2012

    Dear Member,
    We are in process of  migrating our MS SQL 2005 SP2 db engine / SSIS/SSRS services to 2012.Need to know steps/checklist and experiences of migration.
    I have read on Microsoft site (http://msdn.microsoft.com/en-in/library/ms143393(v=sql.110).aspx), that we can only migrate SQL 2005 with SP4 to SQL 2012.Do we need to upgrade first existing 2005 SP2 to SP4 and then start migration.
    Regards,
    Mahesh 

    Hello,
    Yes, you need to apply SP4 first, if you choose to perform an in-place upgrade.
    You have the option to perform a side-by-side upgrade too. Please refer to the following guide:
    http://download.microsoft.com/download/9/5/3/9533501A-6F3E-4D03-A6A3-359AF6A79877/SQL_Server_2012_Upgrade_Technical_Reference_Guide_White_Paper.pdf
    Hope this helps.
    Regards,
    Alberto Morillo

  • SQL 2005 x64 exception

    Recently We've migrated SQL 2005 x86 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3. We migrate users (with standard approach by Microsoft) and application databases
    to new server. Everything is looking ok, applications working. But we've got some SQL exceptions like below.
    Is there any known bug related to that? Could someone help us.
    Memory                              
    MemoryLoad = 15%                    
    Total Physical = 32733 MB           
    Available Physical = 27752 MB       
    Total Page File = 64782 MB          
    Available Page File = 60344 MB      
    Total Virtual = 8388607 MB          
    Available Virtual = 8355366 MB      
    **Dump thread - spid = 84, PSS = 0x00000000D1A43ED0, EC = 0x00000000D1A43EE0                                    
    ***Stack Dump being sent to D:\MSSQL.1\MSSQL\LOG\SQLDump0005.txt                                                
    * BEGIN STACK DUMP:                                                                                             
    *   04/25/14 12:54:30 spid 84                                                                                   
    * ex_handle_except encountered exception C0000264 - Server terminating                                          
    * Input Buffer 255 bytes - 
    There is also some output from debugger:
    0:000> .ecxr
    rax=0000000077207080 rbx=0000000000000000 rcx=0000000016a37d50
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000440
    rip=00000000772070bd rsp=0000000016a38240 rbp=000000000000003f
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000287 r12=00000000032fdab0 r13=0000000000000000
    r14=00000000000019e4 r15=0000000049b8d00c
    iopl=0         nv up ei pl nz na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206
    kernel32!RaiseException+0x3d:
    00000000`772070bd 4881c4c8000000  add     rsp,0C8h
    0:000> kC 1000
    Call Site
    kernel32!RaiseException
    sqlservr!DmpGetClientExport
    sqlservr!_____SQL______Process______Available
    sqlservr!_____SQL______Process______Available
    sqlservr!_____SQL______Process______Available
    sqlservr!SQLExit
    kernel32!UnhandledExceptionFilter
    ntdll!RtlpNotOwnerCriticalSection
    ntdll!_C_specific_handler
    ntdll!RtlIntegerToChar
    ntdll!_C_specific_handler
    ntdll!RtlRaiseStatus
    ntdll!RtlpNotOwnerCriticalSection
    ntdll!LdrGetProcedureAddress
    sqlshield
    sqlservr
    0x0
    0x0
    0x0
    0x0
    0x0
     

    Hi,
    In last days we "close" our SQL to some scanning security applications which could also do some things on our SQL. But it's only a guess. About sqlshield we do the unregister and register DLL's again. Now at last two exception is not the same situation.
    Can you see something from there with "Non-yielding Scheduler". Is it also possible that it something wrong with the hardware. We're using new Cisco rack 1U server for that SQL server. I've also read someting about upgrading the BIOS, related to errors
    "Non-yielding Scheduler". At the end i can also tell, that the server is alive for a couple of days, if there is no a lot activity on the server, i mean on national holidays, through weekend, etc.
    Any new idea?
    Thanks,
    Matjaž
    =====================================================================                                           
           BugCheck Dump                                                                                            
    =====================================================================                                           
    This file is generated by Microsoft SQL Server                                                                  
    version 9.00.5266.00                                                                                            
    upon detection of fatal unexpected error. Please return this file,                                              
    the query or program that produced the bugcheck, the database and                                               
    the error log, and any other pertinent information with a Service Request.                                      
    Computer type is AT/AT COMPATIBLE.                                                                              
    Bios Version is Cisco0 - 0                                                                                      
    BIOS Date: 08/20/13 06:01:31 Ver: 04.06.05                                                                      
    Current time is 11:17:16 04/30/14.                                                                              
    12 Unknown CPU 9., 14 Mhz processor (s).                                                                        
    Windows NT 6.0 Build 6002 CSD Service Pack 2.                                                                   
    Memory                              
    MemoryLoad = 17%                    
    Total Physical = 32733 MB           
    Available Physical = 26900 MB       
    Total Page File = 64782 MB          
    Available Page File = 59543 MB      
    Total Virtual = 8388607 MB          
    Available Virtual = 8355342 MB      
    ***Unable to get thread context - no pss                                                                        
    * BEGIN STACK DUMP:                                                                                             
    *   04/30/14 11:17:16 spid 0                                                                                    
    * Non-yielding Scheduler                                                                                        
    Stack Signature for the dump is 0x00000000000003AD          

  • SQL 2005 cluster rejects SQL logins when in failed over state

    When SQL 2005 SP4 on Windows 2003 server cluster is failed over from Server_A to Server_B, it rejects all SQL Server logins. domain logins are OK. The message is "user is not associated with a trusted server connection", then the IP of the
    client. This is error 18452. Anyone know how to fix this? They should work fine from both servers. We think this started just after installing SP4.
    DaveK

    Hello,
    The connection string is good, you're definitely using sql auth.
    LoginMode on Server_B is REG_DWORD 0x00000001 (1) LoginMode on Server_A is REG_DWORD 0x00000002 (2) Looks like you are on to something. I will schedule another test failover. I assume a 2 is mixed mode? If so, why would SQL allow two different modes
    on each side of a cluster?
    You definitely have a registry replication issue, or at the very least a registry that isn't in sync with the cluster. This could happen for various reasons, none of which we'll probably find out about now, but never the less...
    A good test would be to set it to windows only on Node A, wait a minute and then set it to Windows Auth and see if that replicates the registry setting across nodes correctly - this is actually the windows level and doesn't have anything to do with SQL Server.
    SQL Server reads this value from the registry and it is not stored inside any databases (read, nothing stored in the master database) as such it's a per machine setting. Since it's not set correctly on Node B, when SQL server starts up it correctly reads
    that registry key and acts on it as it should. The culprit isn't SQL Server, it's Windows Clustering.
    Hopefully this makes a little more sense now. You can actually just edit the registry setting to match Node A and fail over to B, everything should work correctly. It doesn't help you with a root cause analysis which definitely needs to be done as who knows
    what else may not be correctly in sync.
    Sean Gallardy | Blog |
    Twitter

  • SQL 2005 to Oracle 10g migration

    We are migrating from SQL 2005 on Windows to Oracle 10g on Linux. If any one has experience with this kind of migration please share the steps involved.
    Also is it possible to migrate subset of data from SQL to Oracle or is migrating entire data/schema the only option?
    Any help or direction in this is much appreciated.Thanks in advance

    Hi spulyala,
    There is no clear and simple way of doing this.
    -The online data move migrates from one java connection/table to another java connection/table so you would need to have the source table already filtered.
    -The offline data move dumps the information out of SQL Server one table at a time, a where clause may be able to be applied manually at this stage, and loads the data in using Oracle sqlldr.
    Of course you can filter and manipulate the tables within SQLServer before migration, within Oracle after migration, and delete table representations from with the tool.
    -Turloch

  • Trying to migrate SQL Server 2000 to Oracle 10g.

    Hi.
    I´m trying to migrate from Sql Server 2000 to Oracle 10g and I got some troubles.
    I have connected both databases with my Oracle Sql Server, after that I went to the Menu--> Migrate--> Fast Migration and then fill all the steps necesary.
    I can see the repository`s table at the oracle schema but after that the Sql Developer hang at the point "capture". I let the tool work for 2 hours and nothing to do. It´s not a hughe db so could be done faster.
    May I miss something?.
    Thanks.

    Hi
    I also have similar issue when trying to migrate from MS SQL 2005 to oracle 10g.
    I use the SQL Developer Version 2.1.0.63.
    First, I tried to use 'Quick Migration' then it created repository then stop there with error message
    "Error ocurred during capture: ORA-01400: cannot insert NULL into ("DDHCOWNER"."MD_PROJECTS"."ID")"
    Then, try manual way to capture SQL server, but some how it doesn't work. It just refresh IDE and stop.
    Before this activity, I tried to migrate MS SQL 2005 using 'Quick Migration' and it works. But this time I have to do it on another DB then this happened.
    So I re-try the previous connection then encountered the same to all.
    Thus, please kindly help to advice how to solve this problem.
    Thank you so much.
    Regards,
    Sai Lin Naung

  • Daily backup on Ms sql server management  studio (MS sql 2005).

    I wander how to perform daily backup on Ms sql server management  studio (MS sql 2005).
    In sql server  Entereprise manager (MS sql 2000) I had no problem to shedule.
    But now I do not find this option

    Hi
    Please follow these steps in SQL Server Management Studio in SQL Server 2005 and <b>award points</b>
    1. Start SQL Server Management Studio.
    2. In the Connect to Server dialog box, click the appropriate values in the Server type list, in the Server name list, and in the Authentication list. 
    3. Click Connect.
    4. In Object Explorer, expand Databases.
    5. Right-click the database that you want to back up, click Tasks, and then click Back Up.
    6. In the Back Up Database - DatabaseName dialog box, type the name of the backup set in the Name box, and then click Add under Destination.
    7. In the Select Backup Destination dialog box, type a path and a file name in the Destinations on disk box, and then click OK.
    8. In the Script list, click Script Action to Job.
    9. In the New Job dialog box, click Steps under Select a page, and then click Edit if you want to change the job parameters.
    Note In the Job Step Properties - 1 dialog box, you can see the backup command.
    10. Under Select a page, click Schedules, and then click New.
    11. In the New Job Schedule dialog box, type the job name in the Name box, specify the job schedule, and then click OK.
    Note If you want to configure alerts or notifications, you can click Alerts or Notifications under Select a page.
    12. Click OK two times.
    You receive the following message:
    The backup of database 'DatabaseName' completed successfully.
    Note To verify the backup job, expand SQL Server Agent, and then expand Jobs. When you do this, the SQL Server Agent service must be running.

  • Fetch the data from the tables in the SQL 2005 server to sap R/3.

    Hi Experts,
    We need to fetch the data from the tables in the SQL 2005 server to sap R/3.
    Please explain which will be the best approach to fetch the same and how to do it. Sample program can greatly help.
    << Please do not offer points >>
    Regards,
    Shobana K
    Edited by: Rob Burbank on Sep 21, 2010 2:36 PM

    Hi,
    Try NATIVE SQL statements in your abap code otherwise you can try to establish jdbc connection from ABAP program.
    search in SDN for samples!
    Suresh

  • Possible for AIR app connecting to SQL 2005 server

    Is it possible using Flex AIR to connection to SQL 2005
    server and fetch data ?
    If YES, whats step / process we need to follow please.
    We have the DB in sql 2005 and we want to develop desktop
    client and fetch the records from DB to AIR app.

    "kamaljeetsinghsaini" <[email protected]>
    wrote in message
    news:gmsmnc$non$[email protected]..
    > As we know that AIR supports SQlite only but in our case
    we want to fetch
    > data
    > from server that is using SQL 2005 as DB. So are you
    saying we can
    > directly
    > send the HTTP service to that server and fetch data from
    it ?
    You can send the HTTPService request to whatever back end
    technology you are
    currently using to access it. For example, if you are using
    ASP.net, you
    would still use ASP.net, but you would send back something
    that Flex
    understands, such as XML, instead of the HTML that the
    browser client
    understands.

  • XServe running MS Windows 2003 server + MS SQL 2005

    I am planning to deploy 3 XServes,
    One running Windows 2003 Server + MS SQL 2005
    the other 2 runnung Windows 2003 Server + MS Terminal Server
    Wonder if there's anyone can share the experience for the above configuration?
    Rgds,
    chiacy

    Digging around Macbytes.com, I came across this article:
    http://weblog.infoworld.com/enterprisemac/archives/2006/12/killtwowindow.html
    To quote:
    "I have tested, and continue to run in a production setting, two instances of Windows 2003 Server hosted by Parallels Desktop, running on OS X Server 10.4.8 on a 3 GHz Xserve. To skip to the punch line, it works, and it's as fast as all get-out."
    HTH
    Xserve Dual 2.3 GHz   Mac OS X (10.3.9)  

Maybe you are looking for