Migration of SQL 2003 to SQL 2012

Hi,
Can someone help me address issue in migrating SQL 2003 to SQL 2012?  What's the best practice in such migration?
Do I need to upgrade it to 2005, 2008 first before migrating it to 2012?  Please advise criticality on this issue and best practice as well.  Thank you.

Hi  arkimuza23,
There is no SQL Server 2003, could you confirm the exact version? If your version is SQL Server 2000, we will be not able to migrate from SQL 2000 to 2012 directly. SQL Server 2012 supports upgrade from only the following versions: SQL 2005 SP4,SQL 2008
SP2,SQL 2008 R2 SP1 or later .
Migration from 2000 to 2012 requires an intermediate step. We will have to make the migration in two steps:
- Step 1: Make a first migration from SQL 2000 to SQL 2008 for instance. You need to be SQL 2000 SP4, then follow this step : Migration SQL Server 2000 to SQL Server 2008
- Step 2: Make a second migration from SQL Server 2008 to 2012.
Supported Version and Edition Upgrades
http://technet.microsoft.com/en-us/library/ms143393.aspx
Migration SQL Server 2000 to SQL Server 2008
http://blogs.technet.com/b/mdegre/archive/2009/07/21/migration-sql-server-2000-to-sql-server-2008.aspx
Thanks,
Candy Zhou

Similar Messages

  • Migrating from DHCP 2003 to DHCP 2012

    Hi,
    i'm planning to migrate from DHCP 2003 to DHCP 2012 or DHCP 2012 R2 failover.
    Saw those instructions:
    extract the configuration in .TXT
    netsh dhcp server export c:\temp\dhcp.txt all
    copy this file on your server 2012 in temp or elsewhere
    import the configuration with this command
    netsh dhcp server import c:\temp\dhcp.txt all
    if you have the error "TLS supported but not configured"
    remove all the option in "Server Option" like 003 Router 006 DNS SERVERS and put it back after doing the import 
    now i have some questions:
    1. is it recommended to build 2 2012 DHCP configured as failover on virtual machines ? (hyper-V)
    2. do those dhcp servers have to or recommended to be DNS also or can they be only DHCP servers ?
    3. my AD functionality level is 2003 - is it a problem for this migration ?
    4. virtual or physical ? whats is recommended ?
    5. any other considerations ?
    TNX

    Hi,
    Virtual or physical will both work. It doesn't matter, as long as the two servers can communicate with each other.
    You do not need DNS installed on the same server, but you can install it without hurting anything.
    I believe that the AD level has no effect because you can have DHCP failover even on workgroup computers.
    -Greg
    http://technet.microsoft.com/en-us/library/dn338983.aspx#specs

  • "The certificate chain was issued by an authority that is not trusted" when migrating to SQL 2012

    Environment:
    1 Primary Site (USSCCM-Site.domain.com)
    1 CAS (USSCCM-CAS.domain.com)
    SQL 2008 R2 (USSCCM-CAS.domain.com)
    SQL 2012 SP1 CU6 (USSQL12.domain.com)
    Issue:
    We were successfully able to migrate the CAS to the new SQL 2012 server, almost without incident. When attempting to migrate the Site instance however, we are getting errors. Screenshot below.
    Attached is a copy of the log. But below is a highlight of what I think are the errors… It appears that either SQL or SCCM doesn’t like a certificate somewhere, but it is contradicting because the logs say that it has successfully tested connection to SQL.
    I am lost.
    Logs stating it can connect successfully to SQL
    Machine certificate has been created successfully on server USSQL12.domain.com.        Configuration Manager Setup                10/21/2013 10:20:10
    AM               2100 (0x0834)
    Deinstalled service SMS_SERVER_BOOTSTRAP_USSCCM-Site.domain.com_SMS_SQL_SERVER on USSQL12.domain.com.  Configuration Manager Setup    10/21/2013 10:20:10 AM              
    2100 (0x0834)
    SQL Server instance [sccmsite] is already running under the certificate with thumbprint[f671be844bf39dec7e7fdd725dc30e225991f28a].       Configuration Manager Setup    10/21/2013 10:20:10 AM        
    2100 (0x0834)
    INFO: Testing SQL Server [USSQL12.domain.com] connection ...                Configuration Manager Setup    10/21/2013 10:20:10 AM      
    2100 (0x0834)
    INFO: SQL Connection succeeded. Connection: USSQL12.domain.com SCCMSITE\MASTER, Type: Unsecure                Configuration Manager Setup    10/21/2013 10:20:10 AM              
    2100 (0x0834)
    INFO: Tested SQL Server [USSQL12.domain.com] connection successfully.  Any preceding SQL connection errors may be safely ignored.            Configuration Manager Setup    10/21/2013
    10:20:10 AM               2100 (0x0834)
    INFO: Certificate: 308202FC308201E4A003020102021011BA47041BB0609D4097BC19F5AB96B5300D06092A864886F70D01010B0500301D311B301906035504031312555353514C31322E7063756265642E636F6D3020170D3133313031373139343632345A180F32313133303932343139343632345A301D311B301906035504031312555353514C31322E7063756265642E636F6D30820122300D06092A864886F70D01010105000382010F003082010A0282010100CFAC23CEA8920051C8C24DF4E96D76D9E034931867C4DBF74F8AE863C5BDE6D1EAEAAF363F6B97DEF1D7A1FC292CB870F353D72F04472EBE3D31DCA009BD3F8C58E2AAB69C892C20598306537F5EEAA43FA6DE55D4A784CEB6FD07486AB2CC2DE1A8651648EBC31A5CD918E8ED6E184FC560B3A8B0F76F83E310BBA8C4EB27F46707E3A6377D8DD06C6808146E407EF9DB464F453798B6C1748216665884A7F2CDE03D9DA1CB4E59E67516E4F345755E35450F84F4B039642851EFFA96B22D8E77EC11C01D389989F740923B58799E34FC8F4F19CD55830FA7E786C993A08A1EEDCA87F209268CE9D5E86AC9E2A14668207721D94ACE9FACE3AA55B53507F6BF0203010001A3363034301D0603551D11041630148212555353514C31322E7063756265642E636F6D30130603551D25040C300A06082B06010505070301300D06092A864886F70D01010B05000382010100A0E33BF490B60C2B8A73BF7FA90EBB69D92DA27B439EF0569650F388EBA34B9F382CEF52DAAB543C2924E1B8DC7BEE828FB0C276330B0FF67340CBFA0CC24F47431E5272DC76C7610C290A04411036441E9822FBF8AB52B4BBE43F5FF48074BA420FF690A94D53AFCEF7AC75E2D2723520A9EF64AF06759814AE92D41CEA2F0D6CC8D9E5DEF121234F5DD97A7E886BE55F57DC0B79052A554724E8A0146C08A74AE75672FBD8C8BD6B7FCA82C1CC69906A45128CDDD1BC3985ED9603C16E712FFBAA8AA6878F853367F3E1F69E727DB96864DF6B47EBDA82659036EC82A8B04E77535CEA314D7518D02C401969C77B91C8C210C57AA991A622D679B994AEED3C               
    Configuration Manager Setup    10/21/2013 10:20:10 AM               2100 (0x0834)
    INFO: Created SQL Server machine certificate for Server [USSQL12.domain.com] successfully.    Configuration Manager Setup 10/21/2013 10:20:10 AM               2100 (0x0834)
    INFO: Configuration Manager Setup - Application Shutdown       Configuration Manager Setup    10/21/2013 10:20:10 AM         2100 (0x0834)
    INFO: Running SQL Server test query.    Configuration Manager Setup    10/21/2013 10:20:10 AM               2100 (0x0834)
    INFO: SQL Connection succeeded. Connection: USSQL12.domain.com SCCMSITE\MASTER, Type: Secure                Configuration Manager Setup    10/21/2013 10:20:10 AM              
    2100 (0x0834)
    INFO: SQL Server Test query succeeded.              Configuration Manager Setup    10/21/2013 10:20:10 AM              
    2100 (0x0834)
    INFO: SQLInstance Name: sccmsite         Configuration Manager Setup    10/21/2013 10:20:10 AM               2100 (0x0834)
    INFO: SQL Server version detected is 11.0, 11.0.3381.0 (SP1).      Configuration Manager Setup    10/21/2013 10:20:10 AM         2100 (0x0834)
    Logs saying certificate is not trusted
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:20:49 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:20:49
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:20:49 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:20:49 AM              
    2100 (0x0834)
    INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure         Configuration Manager Setup                10/21/2013 10:20:49
    AM               2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:20:52 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:20:52 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:20:52
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:20:52 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:20:52 AM              
    2100 (0x0834)
    INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure         Configuration Manager Setup                10/21/2013 10:20:52
    AM               2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:20:55 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:20:55 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:20:55
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:20:55 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:20:55 AM              
    2100 (0x0834)
    INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure         Configuration Manager Setup                10/21/2013 10:20:55
    AM               2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:20:58 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:20:58 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:20:58
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:20:58 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:20:58 AM              
    2100 (0x0834)
    INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure         Configuration Manager Setup                10/21/2013 10:20:58
    AM               2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:21:01 AM              
    2100 (0x0834)
    More logs saying cert is not trusted
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:21:20 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:21:20 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:21:20
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:21:20 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:21:20 AM              
    2100 (0x0834)
    INFO: Updated the site control information on the SQL Server USSQL12.domain.com.    Configuration Manager Setup                10/21/2013 10:21:39 AM              
    2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup    10/21/2013 10:21:39 AM              
    2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.        Configuration Manager Setup   
    10/21/2013 10:21:39 AM                2100 (0x0834)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection                Configuration Manager Setup    10/21/2013 10:21:39
    AM               2100 (0x0834)
    ERROR: SQL Server error: [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection         Configuration Manager Setup    10/21/2013 10:21:39 AM              
    2100 (0x0834)
    *** Failed to connect to the SQL Server, connection type: CCAR_DB_ACCESS.    Configuration Manager Setup                10/21/2013 10:21:39 AM              
    2100 (0x0834)
    CSiteSettings::WriteActualSCFToDatabase: Failed to get SQL connection                Configuration Manager Setup               
    10/21/2013 10:21:39 AM               2100 (0x0834)
    CSiteSettings::WriteActualSCFToDatabaseForNewSite: WriteActualSCFToDatabase(USA) returns 0x87D20002                Configuration Manager Setup    10/21/2013 10:21:39
    AM               2100 (0x0834)
    ERROR: Failed to insert the recovery site control image to the parent database. Configuration Manager Setup                10/21/2013 10:21:39 AM              
    2100 (0x0834)
    Troubleshooting:
    I have read on a few articles of other people having this issue that states to find the certificate on SQL 2012 that’s being used and export it to the SCCM server – which I’ve done.
    http://damianflynn.com/2012/08/22/sccm-2012-and-sql-certificates/
    http://trevorsullivan.net/2013/05/16/configmgr-2012-sp1-remote-sql-connectivity-problem/
    http://scug.be/sccm/2012/09/19/configmgr-2012-rtm-sp1-and-remote-management-points-not-healthy-when-running-configmgr-db-on-a-sql-cluster/
    -Brad

    Hi,
    How about importing certificate in the personal folder under SQL server computer account into SCCM server computer account or SCCM server service account? That certificate is for SQL Server Identification. And you could
    set the value of the ForceEncryption option to NO. (SQL Server Configuration Manager->SQL Server Network Configuration->
    Protocols for <server instance>->Properties)
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Issues with Shell32.dll, NTDLL.DLL and Migration from Windows 2003 to Windows 2012

    Hello all,
    I am new to ThinApp and working as a consultant to help a company migrate older Windows 2003 software to Windows 2012.  They have purchased ThinApp 5.0.4.5 so that is what we will be using.
    We have created a clean 2003 VM and did a pre-scan
    We loaded the application and configured it  and then did a capture.
    We then tested the capture the 2003 VM and it works
    We then loaded the capture on a Clean 2003 VM and it works
    We then loaded onto a 2012 VM and when running the app from a command window get an error  -missing import shell32.dll:StrCpyNW
    If we run the capture in Emulation Mode on 2012 VM, we do not get the Shell32.dll error but instead the cmd fails with a Fault Module Name  - NTDLL.DLL error
    I am sure I am just missing the correct location to identify or configure the capture - but do not have the experience to know where yet.  (Taking training next week).
    Until then, is there any suggestions which I can try?
    Thanks for your time in advance,
    Vince 

    Tried and done that.  The main issue while configuring the printer from the printer Web Interface is that there is no access to the Digital Sending section due to a problem with the "Sun Java plug in"  I think the code mentions 1.31. or similar.
     We downloaded the java plug in and installed it.  No progress. 
    We reset the printer to defaults and reconfigured it .. It sees the smtp gateway and access it but fails sending email with scanned documents.. 
    We have tried in very different ways.  We connected the printer to another domain SBS server 2003 and it works beautifully.  So, I have no idea on what is the problem. We created a firewall exception for ports 390. 1783 from the SBS to the Printer
    and still no go..
    We have tried four different accounts and nothing.  Same results as stated originally.
    Any other suggestions??
    JFM

  • Best practice for client migration from SMS 2003 to SCCM 2012 R2?

    Can anyone advise what the most recommended method is for migrating SMS 2003 clients (Windows 7) to SCCM 2012 R2?
    Options are:
    1. SMS package to deploy ccmclean.exe to uninstall SMS 2003 client. Deploy SCCM 2012 R2 client via SCCM console push.
    2. Simply push SCCM client from console installing over existing SMS 2003 client.
    I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
    3. Use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean and then install the SCCM client.
    Appreciate any feedback. Thank you.

    Hi,
    >>I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
    I haven't seen any official document records the option 2 method. There is only upgrading from SCCM 2007 to SCCM 2012 directly.
    I think you could use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean.exe. Then use SCCM 2012 to discover these computers and push clients to them.
    Best Regards,
    Joyce

  • Migrating from Server 2003 to Server 2012 Essentials or new install?

    We have a small network having downsized some years ago. Currently we have two 2003 servers  and 6 workstations. Originally we were running Exchange on one of the servers, but now Exchange is remotely hosted. I have a new server that will be
    running Essentials. I want to replace both of the old servers and just have the one new server. I am thinking that with such a small network, it will be easier just setting up the new server in a new domain rather than migrating. Does this make sense? Any
    pitfalls to be aware of?
    Thanks,
    Mike

    Hi Mike,
    à
    I am thinking that with such a small network, it will be easier just setting up the new server in a new domain rather than migrating.
    Does this make sense?
    Based on your description, setting up the new server or performing a migration, will depend on the target which
    you want to achieve.
    For migration, it will help you to migrate the settings and data from that old server to the new server. For
    more details, please refer to following article and check if can help you.
    Migrating
    to Windows Server 2012 Essentials
    If just set up the new server, as you mentioned, it may be easier than migrating. For more details, please refer
    to following article and check if can help you.
    Install Windows Server Essentials
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • SQL 2012 Databse Migration to Windows Azure SQLDatabase

    Hello Experts
    Please advise on the following issues, thank you.
    If we want to migrate a SQL 2012 database to windows Azure SQL Database by implementing the Contained database features, can you pleas explain the procedures or steps, thank you for your help as always.
    Regards

    Hi,
    Here are some links on deploying database to SQL Azure.
    How to Deploy a Database to Azure
    http://azure.microsoft.com/en-us/documentation/articles/sql-database-deploy/
    How to Migrate an On-Premises SQL Server 2012 Database to Windows Azure SQL Database
    http://blogs.msdn.com/b/brunoterkaly/archive/2013/09/26/migrating-an-on-premises-sql-server-2012-database-to-windows-azure-sql-database.aspx
    Using the Deploy Database to SQL Azure Wizard in SQL Server Management Studio to move to the Cloud
    http://www.mssqltips.com/sqlservertip/3035/using-the-deploy-database-to-sql-azure-wizard-in-sql-server-management-studio-to-move-to-the-cloud/
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Which is the best way to migrate the SQL SERVER 2000 Database to SQL SERVER 2003 Database?

    Hi,
        I  need to migrate the Production database sql server 2000 to Sql server 2003, Please give me the best idea to migrate the database without any loss data, credentials and  Objects. 
    Nandha Kumar

    SQL server does not have any version named SQL server 2003 please check the version correctly it should be either SQL 2005,2008,2008 R2,2012
    You can use the backup/restore to upgrade the SQL 2000 database to till SQL 2005,2008,2008R2
    For SQL Server 2000 to 2012
    First upgrade from SQL 2000 database to either SQL 2005, 2008 or 2008R2 and than upgrade it to SQL 2012.
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/eaa1eb44-729f-466b-8233-cb768fbb4208/upgrading-to-sql-server-2008-from-sql-server-2000?forum=sqlsetupandupgrade
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4fac7511-2c75-46a0-802b-807dd26b12bf/sql-2012-will-not-convert-a-sql-2000-database?forum=sqlservermigration
    And after migration to SQL 2005 or 2008, if you want to script the database than can generate scripts pick DB and check off "script all objects in the selected database".
    http://blog.sqlauthority.com/2011/05/07/sql-server-2008-2008-r2-create-script-to-copy-database-schema-and-all-the-objects-data-schema-stored-procedure-functions-triggers-tables-views-constraints-and-all-other-database-objects/
    You can upgrade from SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 to SQL Server 2012.
    http://msdn.microsoft.com/en-us/library/ms143393(v=sql.110).aspx
    Please click the Mark as answer button and vote as helpful if this reply solves your problem

  • File opening throws RBS exception after migrating to a new farm with sql 2012

    We have successfully migrated the SP 2010 -sql 2008 r2 wss_content to a new sp2010 farm with sql 2012. The old and new farms are configured for RBS - FIlestream.
    In the new farm when tried opening a document we see the below exceptions in event viewer. The documents open fine for admin users and fail for others. I have verified all the permissions on the blob store file location and it looks good. Users have no 
    issue uploading new files over and below the set the file size limit.
    Any suggestions on how to debug this would be great, do we need to rerun the .migrate() to realign any of the blob file references, we played around setting the max file size couple of times.
    Event vwr on DB server -
    FILESTREAM file named with GUID '00311100-0000-51eb-f3a8-0b387bc5c5ce' that belongs to FILESTREAM data file ID 0x10001 does not exist or cannot be opened.
    Event vwr on Front end -
    Message ID:20, Level:ERR , Process:10580, Thread:36
    Blob store <FilestreamProvider_1> threw this exception:
    Operation: Unknown
    BlobStoreId: 1
    Log Time: 5/5/2014 8:00:49 PM
    Exception: Microsoft.Data.SqlRemoteBlobs.BlobStoreException: There was a generic database error. For more information, see the included exception. ---> System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from
    the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
       at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
       at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
       at System.Data.SqlClient.TdsParserStateObject.ReadByteArray(Byte[] buff, Int32 offset, Int32 len)
       at System.Data.SqlClient.TdsParserStateObject.ReadInt64()
       at System.Data.SqlClient.TdsParserStateObject.ReadPlpLength(Boolean returnPlpNullIfNull)
       at System.Data.SqlClient.TdsParser.ProcessColumnHeader(SqlMetaDataPriv col, TdsParserStateObject stateObj, Boolean& isNull)
       at System.Data.SqlClient.SqlDataReader.ReadColumnHeader(Int32 i)
       at System.Data.SqlClient.SqlDataReader.GetBytesInternal(Int32 i, Int64 dataIndex, Byte[] buffer, Int32 bufferIndex, Int32 length)
       at System.Data.SqlClient.SqlDataReader.GetBytes(Int32 i, Int64 dataIndex, Byte[] buffer, Int32 bufferIndex, Int32 length)
       at Microsoft.Data.BlobStores.FilestreamBlobStore.FilestreamStoreLibraryBase.ReadBlob(Byte[] storePoolId, Byte[] storeBlobId)
       --- End of inner exception stack trace ---
       at Microsoft.Data.BlobStores.FilestreamBlobStore.FilestreamStoreLibraryBase.ReadBlob(Byte[] storePoolId, Byte[] storeBlobId)
       at Microsoft.Data.BlobStores.BlobStore.ReadBlobInternal(Request request)
    BlobStoreException Code: OperationFailedAuthoritative
    -Mash "http://sharepointxperiments.wordpress.com"

    Migration - its a content db backup/restore/mount to new farm with sql 2012 from sql 2008 r2
    Okie here are the results after we tried to narrow down the issue to few steps-
    This issue happens on documents that are already existed in the content db prior to migration. we picked two docs from one library. DOC A and DOC B of close to same size..
    DOC A - file size 64k, rbs max size set to 1mb.
    Regular User and SPAdmin both can open fine, check out n check in successfully.
    no entries made in event vwr of front end and DB server
    DOC B - file size 64k, rbs max size set to 1mb
    SPAdmin - can check out n open fine, but cannot check in back - file not available error
    Regular User - cannot open the file - file not avialable at the url
              Both users can view doc properties at lib level..
    Errors found in event vwr of DB server -
    "FILESTREAM file named with GUID '00311100-0000-51eb-f3a8-0b387bc5c5ce' that belongs to
    FILESTREAM data file ID 0x10001 does not exist or cannot be opened."    
    and
           "The operating system returned the error '2(The system cannot find the file specified.)' while attempting 'FsDoHandler::CreateFile' on 'H:\Blob_Store\a06953ae-6f49-43b1-9c2d-fefb13bda9fe\1c581a4a-b450-4143-bc3d-8d419b49b0fb\0000eb20-000066ff-0002'
    at 'fstrman.cpp'(2075)."
    I incline to believe that the references for documents in blob store could have been corrupted for some documents during the migration. Any new docs uploaded to content or to blob are all accessible fine.
    I'm not sure running .migrate() will re align the blob file references? Any ideas on how to effectively get this resolved..
    -Mash "http://sharepointxperiments.wordpress.com"

  • Migration of the database from Microsoft SQL 2014 Express to Microsoft SQL 2012 Server

    I posted a similar thread yesterday, and I realized that there was a serious typo.
    Link: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b3e201ea-6c7c-43a4-8908-842b714ea451/migration-of-the-database-from-microsoft-sql-2014-express-to-microsoft-sql-2012-server?forum=sqlservermigration
    Therefore, I made a decision to post another thread right now.
    I am
    writing to ask if there are any known issues when migration from MS SQL 2014 Express to MS SQL 2012 Server version. Are there any step-by-step instruction on how I can go about doing this?
    Looking forward to your response. Thank you for your time.
    Regards,
    Jeff Yoo 

    Hello,
    SQL Server 2012 setup program won’t allow you to perform a downgrade from SQL Server 2014 Express Edition. Backup/Restore
    and Detach/Attach won’t help you either.
    One option you have left is using SQL Server Import/Export Wizard as explained on the following article.
    http://www.mytechmantra.com/LearnSQLServer/Downgrade_SQL_Server_Database_P1.html
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Steps SSIS and SSAS Migration from sql server 2005 to 2012?

    steps SSIS,SSRS and SSAS Migration from sql server 2005 to 2012? any precautions to take while migration.
    any documentation or any specified steps.

    Hi Vijay,
    According to your description, you want to migrate SQL Server Integration Services and SQL Server Analysis Services from SQL Server 2005 to SQL Server 2012.
    For how to migrate SQL Server Integration Services, please refer to the article:
    http://www.bidn.com/blogs/DevinKnight/ssis/2718/upgrading-packages-to-ssis-2012.
    In addition, since the issue regards SQL Server Integration Services. I suggest you post the question in the SQL Server Integration Services forums at
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlintegrationservices.
    For how to migrate SQL Server Analysis Services, please refer to this article:
    http://www.codeproject.com/Articles/435703/Migration-from-SQL-server-to.
    In addition, since the issue regards SQL Server Analysis Services. I suggest you post the question in the SQL Server Analysis Services forums at
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlanalysisservices. It is appropriate and more experts will assist you.
    Regards,
    Michelle Li

  • 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

  • Deprecated Code - Migration from SQL 2005 to 2012

    Hi,
    We're planning to upgrade our database from SQL Server 2005 to 2012. Based on this
    link, it seems there's no code conversion needed in terms of Data Type, Keywords in creating SPs, Function, trigger.
    The only thing that concerns me is this
    Set options
    SET ROWCOUNT for INSERT, UPDATE, and DELETE statements
    TOP keyword
    SET ROWCOUNT
    109
    But other than that, it should be good.
    I would also like to get any feedback from other user who migrated their database from 2005 to 2012. What were the issues encountered during the process. Any tips and suggestion will be much appreciated.
    Many Thanks.

    What is your mode of upgrade
    1. In place
    2. Side by side
    You must also read
    Breaking changes to DB engine features in SQL Server 2012
    Breaking changes to SQL Server features in SQL Server 2012
    If you are just using DB engine features and SSIS I would advise you to first run upgrade advisor and look for breaking changes or unsupported scenarios. make sure you mitigate all such issues.
    There is also a feature where you can side by side upgrade database by backup restore to SQL Server 2012 and still keep
    compatibility level to 90
    (but that is not advised)
    I have migrated database from 2008 to 2012 but not from 2005 but above documents were very handy and would work quite well.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Migrating SCCM 2007 R2 database to SQL 2012

    Am I able to migrate my SCCM 2007 R2 database from SQL 2008 (running in 2005 compatibility mode) to SQL 2012? Is it even supported to run a 2012 instance with compatibility set to 2005? Or will I need to upgrade the database at some point to get this to
    work.  
    Currently, my attempts fail and the errors in the ConfigMgrSetup.log suggests an issue with compatibility:
    Incorrect syntax near '99900'. : ins_upd  
    Incorrect syntax near '99901'. : ins_upd 
    -which led me to a hotfix (http://support.microsoft.com/kb/2676776) that, upon installing, indicated that it failed to completely install. 
    For whatever it's worth, the SCCM server is running 2008 x64 and the SQL server is 2008 R2. 

    See the caveats at http://technet.microsoft.com/en-us/library/ee344146.aspx listed under the SQL Server Site Database Configurations section:
    "To use SQL Server 2012 to host the site database, you must install the following updates as described in the Microsoft
    Knowledge Base:
    Article 2676737 
    Article 2676776 
    Additionally, to use SQL Server 2012 for the site database, you must upgrade the instance of SQL Server in use at a site from SQL Server 2008 or SQL Server 2008 R2 to SQL Server 2012. It is not supported to install a new Configuration
    Manager 2007 SP2 site with SQL Server 2012. It is also not supported to install Configuration Manager 2007 R3 when SQL Server 2012 is in already in use for the site database."
    Jason | http://blog.configmgrftw.com

  • Migrating SQL 2008 DB to SQL 2012 for SharePoint Farm

    Our SharePoint 2013 Farm runs on ISCSI Disk on Windows 20008 R2 Standard SP1 Platform with SQL 2008 R2 Standard SP2.
    Now we are planning to move this ISCSI Disk to another SQL 2012 Standard Platform and then upgrade the SQL 2008 Databse to SQL 2012. Can some one please let me know what challenges we might face during this implementation.

    http://technet.microsoft.com/en-us/library/cc512723(v=office.14).aspx
    It depends if you want to move all, or just some, of your databases to the new server. If you need to move all of them that link describes the process but in short;
    Backup and restore all databases to the new server
    Configure the server roles and logins for the SharePoint accounts on SQL
    Create (or modify) your SQL alias to point to the new server

Maybe you are looking for