SQL 2005 & 2012

We have a server with SQL 2005 on it. We just installed SQL 2012. When I look in the services there is also an instance called SQLEXPRESS. When I go into the control panel to uninstall a program I do not see any SQL Express installed.
I have stopped the SQL express instance and am trying to start the SQL 2005 and SQL 2012 instances at the same time. We need the 2005 to be started to be able to look at the current system and 2012 needs to be started at the same time as we are
trying to redo the system in SQL 2012. Does anyone know why we can not start both instances at once. If one is running and I try and start the other instance I get "Windows could not start the SQL Server (MSSQL2012) on Local Computer.
For more information, review the System Event log. If this is a non-Microsoft service, contact the service vendory, and refer to service-specific error code 10048." When I look in the System event log I see the following "The SQL Server
(MSSQL2012) service terminated with service-specific error Only one usage of each socket address (protocol/network addres/sport) is normally permitted." Can anyone give me some information as to what the problem may be. Thanks in advance.

I have previously tried stopping 2005 and 2012 and starting one before the other, while rebooting the server in between. However, I always got the same error regardless of which SQL was started first.
Thanks for the information/link. I stopped all SQL, started 2012, and then tried to start 2005 using the link you provided.
Most of it appears to be OK until I get near the end of the output and then I see the following errors:
(1) error: 26023, Severity: 16, State: 1
Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
(2) error: 17182, Severity: 16, State 1
TDSSNIClient initialization failed with error 0x2740, status code 0xa.
(3) error: 17182, Severity: 16, State: 1
TDSSNIClient initialization failed with error 0x2740, status code 0x1.
(4) error: 17826, Serverity: 18, State: 3
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
(5) error: 17120, Severity: 16, State 1
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
In looked in the event logs I see the errors above and a warning (at the same time stamp) that says: "MSDTC encountered an erro (HR=0x80000171) while attempting to establish a secure connection with system".
In looking in the event log for SQL 2012 (since 2005 is not running) I do not see any errors.

Similar Messages

SQL 2005 will not connect in SQL 2012 profiler

We have a few SQL 2005 databases that we manage. I went to do a trace on them(recently upgraded to 2012) and it gives me the error, "SQL Server Native Client 11.0 does not support connections to SQL Server 2000 and earlier versions".
According to MSDN it does. https://msdn.microsoft.com/en-us/library/cc280356(v=SQL.110).aspx
"SQL Server Native Client 11.0 supports connections to SQL Server 2005, SQL Server 2008, SQL Server 2008
R2, SQL Server 2012, and Windows Azure SQL Database."
Any clue why it wouldn't let me connect?

Can you specify the following parameter in the "connect to server" dialog when you load the Profiler --> click on "options" button and go to "Additional Connection Parameters" tab and paste the following?
DataTypeCompatibility=80
Satish Kartan www.sqlfood.com

SQL Server 2005 performance decreases with DB size while SQL Server 2012 is fine

Hi,
We have a C# windows service running that polls some files and inserts/updates some fields in database.
The service was tested on a local dev machine with SQL Server 2012 running and performance was quite decent with any number of records. Later on the service was moved to a test stage environment where SQL Server 2005 is installed. At that point database
was still empty and service was running just fine but later on, after some 500k records were written, performance problems came to light. After some more tests we've founds out that, basically, database operation performance in SQL Server 2005 decreases with
a direct correlation with the database size. Here are some testing results:
Run#
1
2
3
4
5
DB size (records)
520k
620k
720k
820k
920k
SQL Server 2005
TotalRunTime
25:25.1
32:25.4
38:27.3
42:50.5
43:51.8
Get1
00:18.3
00:18.9
00:20.1
00:20.1
00:19.3
Get2
01:13.4
01:17.9
01:21.0
01:21.2
01:17.5
Get3
01:19.5
01:24.6
01:28.4
01:29.3
01:24.8
Count1
00:19.9
00:18.7
00:17.9
00:18.7
00:19.1
Count2
00:44.5
00:45.7
00:45.9
00:47.0
00:46.0
Count3
00:21.7
00:21.7
00:21.7
00:22.3
00:22.3
Count4
00:23.6
00:23.9
00:23.9
00:24.9
00:24.5
Process1
03:10.6
03:15.4
03:14.7
03:21.5
03:19.6
Process2
17:08.7
23:35.7
28:53.8
32:58.3
34:46.9
Count5
00:02.3
00:02.3
00:02.3
00:02.3
00:02.1
Count6
00:01.6
00:01.6
00:01.6
00:01.7
00:01.7
Count7
00:01.9
00:01.9
00:01.7
00:02.0
00:02.0
Process3
00:02.0
00:01.8
00:01.8
00:01.8
00:01.8
SQL Server 2012
TotalRunTime
12:51.6
13:38.7
13:20.4
13:38.0
12:38.8
Get1
00:21.6
00:21.7
00:20.7
00:22.7
00:21.4
Get2
01:38.3
01:37.2
01:31.6
01:39.2
01:37.3
Get3
01:41.7
01:42.1
01:35.9
01:44.5
01:41.7
Count1
00:20.3
00:19.9
00:19.9
00:21.5
00:17.3
Count2
01:04.5
01:04.8
01:05.3
01:10.0
01:01.0
Count3
00:24.5
00:24.1
00:23.7
00:26.0
00:21.7
Count4
00:26.3
00:24.6
00:25.1
00:27.5
00:23.7
Process1
03:52.3
03:57.7
03:59.4
04:21.2
03:41.4
Process2
03:05.4
03:06.2
02:53.2
03:10.3
03:06.5
Count5
00:02.8
00:02.7
00:02.6
00:02.8
00:02.7
Count6
00:02.3
00:03.0
00:02.8
00:03.4
00:02.4
Count7
00:02.5
00:02.9
00:02.8
00:03.4
00:02.5
Process3
00:21.7
00:21.0
00:20.4
00:22.8
00:21.5
One more thing is that it's not Process2 table that constantly grows in size but is Process1 table, that gets almost 100k records each run.
After that SQL Server 2005 has also been installed on a dev machine just to test things and we got exactly the same results. Both SQL Server 2005 and 2012 instances are installed using default settings with no changes at all. The same goes for databases
created for the service.
So the question is - why are there such huge differences between performance of SQL Server 2005 and 2012? Maybe there are some settings that are set by default in SQL Server 2012 database that need to be set manually in 2005?
What else can I try to test? The main problem is that production SQL Server will be updated god-knows-when and we can't just wait for that.
Any suggestions/advices are more than welcome.

...One more thing is that it's not Process2 table that constantly grows in size but is
Process1 table, that gets almost 100k records each run....
Hi,
It is not clear to me what is that you are doing, but now we have a better understanding on ONE of your tables an it is obviously you will get worse result as the data become bigger. Actually your table look like a automatic build table by ORM like Entity
Framework, and it's DDL probably do not much your needs. For example if your select query is using a filter on the other column that [setID] then you have no index and the server probably have to scan the entire table in order to find the records that you
need.
Forum is a suitable place to seek advice about a specific system (as I mentioned before we are not familiar with your system), and it is more suitable for general questions. For example the fact that you have no index except the index on the column [setID]
can indicate a problem. Ultimately to optimize the system will need to investigate it more thoroughly (as it is no longer appropriate forum ... but we're not there yet). Another point is that now we can see that you are using [timestamp] column, an this
implies that your are using this column as a filter for selecting the data. If so, then maybe a better DDL will be to use clustered index on this column and if needed a nonclustered index on the [setID] if it is needed at all...
what is obviously is that next is to check if this DDL fit
your specific needs (as i mentioned before).
Next step is to understand what action do you do with this table. (1) what is your query which become slowly in a bigger data set. (2) Are you using ORM (object relational mapping, like Entity Framework
code first), and if so then which one.
[Personal Site] [Blog] [Facebook]

Migrate biztalk 2006R2/SQL server 2005 projects to Biztalk 2013/SQL server 2012

We have Biztalk application projects deployed on Biztalk 2006R2/SQL server 2005 environment on a single server
Now we have installed and configured Biztalk 2013/SQL server 2012 in a multicomputer environment where Biztalk server is on one computer while SQL server is on the other.
Now it's time to migrate the projects 2006R2 to 2013.. Is it a smooth process? I found a lot of posts about migration from 2006R2 to Biztalk 2010... Just wondering if it is similar or more complex?? Appreciate any help/suggestions.. thanks!!

Hi Annee,
Following article should answer your question:
BizTalk Application Migration Guide
Also have a look at following forum post:
http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral
Maheshkumar S. Tiwari|http://tech-findings.blogspot.in/

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Run Reporting services 2005 with databases housed on SQL Server 2012?

Hi, I have a RS 2005 install in which the ReportServer and ReportServerTempDB databases reside on a different SQL Server 2005 server. I am planning to upgrade DB server to 2012 and would like to keep SSRS as 2005.As a second phase I will upgrade SSRS2005
to SSRS 2008. So I would be running something like this:
Server A: SQL 2005 Reporting Services
Server B: SQL 2012 database engine - housing ReportServer and ReportServerTempDB
Is this configuration supported?

Hello,
According to the
BOL, Report Server service checks the database version at startup. If the report server is connected to a database that is an earlier version, the report server will update the database during startup.If you have a newer report server database, you
cannot use it with an earlier version of a report server instances.
In that case, the earlier versions of SQL Server Database Engine that can be used to host the SSRS report server databases. For example, In SQL Server 2005 Reporting Services, we can use either SQL Server 2000 or SQL Server 2005 to host the databases, for
SSRS 2012, we can use SQL Server 2012,2008 R2,2008,2005.
Based on my test, In the Reporting Services 2005 Configure Manager, we can create a new database on a remote SQL Server 2012 database engine and the Initialization is successful.
In this way, the databases are created from the script file which installed with the Reporting Services instance, you can find the Catalog.sql and CatalogTempDB.sql under folder C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer.
However, when upgrade the existing ReportServer database and ReportServerTempDB database on the SQL Server 2012 by restore from a backup, we cannot use this existing database for Reporting Services 2005 and get the following message:
The database version (162) does not match your reporting serivces installation.And the initialization failed.
In your case, you can host the ReportServer database and ReportServerTempDB database of SSRS 2005 on SQL Server 2012 database enginer by create a new database from Reporting Services 2005 Configure Manager. But you cannot use the existing
database which upgrade to SQL Server 2012.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

SSRS 2012 rendering issue/Enabling Anonymous access - Upgraded SSRS from SQL 2005 to SQL 2012.

Hi,
I just recently upgraded SQL 2005 SSRS to SQL 2012 SSRS. Everything is working great other than small issue.
Sounds like some authentication issue. SQL 2005 SSRS - IIS, we enabled anonymous access and we never had this problem. SQL 2012 SSRS /WIN 2008 R2 - I am not sure how to enable anonymous access.
If anyone can help me on this? I really appreciate your help.
Thanks,
Vel
Vel Thavasi

Hi Vel,
According your description, you want to know how the enable anonymous access to SSRS 2012. Right?
In SSRS 2008 or later version, we are not using IIS any more. If we want to configure the authentication, we need to configure in RSReportServer.config. This file locate at:
<drive>:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer
However, in SSRS 2012, Anonymous authentication is not supported on report server. Please see:
Authentication with the Report Server
In this scenario, we need to custom an authentication type to achieve the "Anonymous" goal. Please refer to the link:
Configure Custom or Forms Authentication on the Report Server
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

SQL 2005 discoveries after upgrade to Operations Manager 2012 R2 UR3 upgrade

Hi
We did a (succesfull) upgrade of our SCOM 2012 SP1 environment to 2012 R2 UR3. We noticed after the upgrade that databases of some SQL 2005 clustered instances on Windows 2003 R2 SP2 are no longer discovered. checking the eventlog shows the eventid
21405 on the DiscoverSQL2005DB.vbs disvovery (process exited with 4294967295)
Browsing and checking several webfinds didn't provide a solution yet. Perhaps I overlooked the obvious....
Possible solutions which didn't bring relief yet:
check on SQL SP's
WMI registry settings [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM] ": Low/High Threshold On Events
WMI repair, mofcomp...
Uninstall/Reinstall Monitorring Agent
manual run of the discover script returns all info
The runas discover and monitor account(s) are local admin on the OS and SA on the SQL instances
I'm stuck: right now we wanted to present some distributed applications through LiveMaps in scom to our internal customers and some essential databases are no longer discovered/monitorred.
Any help highly appreciated

I'd just like to add that since upgrading all of our environments to 2012 R2 UR3, we are receiving multiple alerts for multiple script failures - e.g. Events 21404, 21405 to name a couple.
I have logged a few Microsoft Premier Support Calls and they are still working on them.
We get this on all SQL 2005,2008 running on Windows Server 2003. Microsoft's response to this is:
"This is a known bug in the latest SQL MP. This is due to the problem with the DiscoverSQL2008DBEngineDiscovery.vbs and DiscoverSQL2005DBEngineDiscovery.vbs scripts which contains the following line of code :
tcp = oQuery.ItemIndex(0).PropertyStrVal
The issue is the ItemIndex is supported only on Vista+ operating systems. The product group is currently investigating and evaluating the issue and I don’t think the fix will be released recently…"
I guess that meant "any time soon' :)
I should add that we also upgraded the SQL MPs around this time too, to 6.5.1.0.
So as you can appreciate, we just have to put up with this for now!
Cheers

Can't restore SQL 2005 BAK to SQL 2008 R2 running on Server 2012

Hi there,
Preparing to switch from SQL 2005/Server 2003 to SQL 2008 R2 / Server 2012. Took a backup of the SQL database on 2005 (stored at a cloud backup provider nightly) and copied to the new machine. Unable to restore the .BAK file, with the error:
The media family on device <backup path> is incorrectly formed. SQL Server cannot process this media family.
RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)
Tried it with two different backup files from two different nights, same error. I understand that this error can show up when restoring to a lower version of SQL, but that's not the case here.
Also, I know this can occur if the BAK file is corrupt, and I can't verify that yet, but two in a row failed. I'm hoping our cloud solution isn't part of the problem somehow.
BAK file is 15 Gb in size, so don't have the ability to attempt the restore on the 2005 production server. Just not enough room, and can't afford to cause performance issues on that box anyway.
Anyone know of any way to get a better handle on what's going on, or, even better, how to resolve it?
Thanks
Robin

Hello,
Since you are using a cloud solution, maybe the following article applies in your scenario.
http://www.sqlcoffee.com/Troubleshooting047.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Can Reporting Services 2005 report on SQL Server 2012 database?

We would like to upgrade our SQL Server from Standard 2005 to Enterprise/Standard 2012. Unfortunately, we also have a lot of reports based on Reporting Services 2005. If possible we would like avoid upgrading them at this time.
Is it possible to run Reporting Services 2005 of SQL Server 2012? If yes then is there pre-requiste like drivers or dll or any other to connect SSRS 2005 to SQL server 2012?
If we run Reporting Services 2005 of SQL Server 2012 then do we will face performance lag issue due to version difference of SSRS 2005 and SQL server 2012?

Moderators,
Can anyone merge this -
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2c44351c-35b4-4208-a2b7-88fc810d53ff/can-reporting-services-2005-report-on-sql-server-2012-database?forum=sqlreportingservices
sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **.

Upgrade Process from SQL 2005 to SQL 2012

Hi All,
I have gone thru multiple threads and would like to understand some steps in detail for me to upgrade SQL 2005 to SQL 2012.
Below is my understanding and questions around it, I would be setting up a new environment with OS 2007/2008 with SQL 2012:
Environment Readiness - Ensure new environment is ready with Win 2007/2008 with SQL 2012 Server
Run Upgrade Advisor on the new environment and point to SQL 2005 instance
Find the breaking/discontinued changes to be done before or After Upgrade
<Question>: Over here I would like to know what should be our approach to make the required changes
<Question>: Obviously I should not be making changes directly on the Production SQL 2005 server, then in that case should I take a backup/restore on the new SQL Server 2012 and then make the required changes to the database objects
like (Table schema(changing column names/datatypes etc.), Stored Procedure, Functions & Views)
<Question>: When I do a backup/restore I would also get the data along with it, so is this a recommended approach or should we only run/use the table schema creation scripts, fix the issues identified by UA and then do an Table to Table import,
any thoughts on this ?
<Question>: If I have to do a table to table Import then I should ensure there's a downtime during the Import or would I have any other better approach
So, basically my questions are around the approach of fixing the issues identified by UA and moving the database to SQL Server 2012 environment, I have around 300 databased to me upgraded.
Please do let me know what should be a good/proven approach ? Pl. do let me know if you would need any more details from me.
---Umesh

Thanks all for the replies.
I am trying summarize what I have understood here:
Document SQL Server 2005 environment details, Is there any tool which could give us all relevant details
I would take the backup from the SQL Server 2005 Production environment and then restore the same in a test environment which again has SQL Server 2005 and Run Upgrade Advisor on that
Probbaly run SQL Profiler as well to find out the deprecated changes to be done
I should fix all the breaking, discontinued changes on the Test system identified by UA
I should fix all the deprecated changes on the Test system identified by SQL Profiler
Steps 3 & 4 should give me the changed scripts for all database objects (i.e. Table Schema, Stored Procedures, Functions & Views)
<Question> Perform test, I understand this acitivity test can be captured by having SQL profiler running in the background on the SQL Server 2005 production environment where we can identify some days in a week or a month where maximum activity is
expected to ensure we cover most the scenarios, let me know is this approach looks fine or is there a better approach
Now, with regards to acutal upgrade I need to identify a time window where in less activity is done during which I could have a downtime for the actual SQL Server 2005 production environment
Post downtine, I should do a BackUp for all databases from SQL Server 2005 production environment
Test on environment readiness of SQL Server 2012 can be compared against the documentation done as part of the first Step
<Question> Ideally I should a restore first in the new environment which has SQL Server 2012
<Question> Then run the Scripted changes where we fixed all the breaking, discontinued & deprecated changes
<Question> Does above sequence of Step 9 & 10 make sense or is there a better approach of doing it
<Question> Post Upgrade and running of changed scripts, I should run the Upgrade Advisor again and see if everything looks fine
<Question> Perform test again which we ran on SQL Server 2005 Test environment
<Question> These steps should complete the Upgrade process.
Please do let me know if the above sequence look ok to all of you and does it really work in a practical scenario, do let me know your feedback or any change in sequence/process or any other tools that can be used here.
Thanks Again ...

SQL 2005 to SQL 2012 Replication for SSRS

I recently successfully implemented one-way log shipping from a production SQL 2005 database to a new SQL 2012 database in the hopes that I can use the 2012 database to run SSRS 2012 on it.
Unfortunately, the 2012 database is kept offline since log shipping between two DIFFERENT SQL versions can only be done in a NO RECOVERY mode. (Standby mode is NOT available which would make the SQL 2012 read only and therefore workable for SSRS
2012.)
Does anyone have any suggestions on if there is another method on how to achieve this?

Yes, You can try replication. I hope you've latest service pack upgrade for SQL 2005.
http://msdn.microsoft.com/en-us/library/ms143699.aspx
BOL:-
A Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server 2005 Publisher can have Subscribers running SQL Server 2005, SQL Server 2008 (including SQL Server 2008 R2), or SQL Server
2012; and a SQL Server 2012 Publisher can have Subscribers running SQL Server 2005, SQL Server 2008 (including SQL Server 2008 R2), or SQL Server 2012.
-Prashanth
-Prashanth

Logshipping from SQL 2005 to SQL 2012

I have a 2005 primary sql database (production-constantly updated). I would like to have (pseudo) real time copy in a secondary 2012 sql server instance. I want to run SSRS 2012 on this new secondary server. The end goal is to have users
access 2012 SSRS (uninterrupted) on the secondary server with a copy of "real-time" data from the primary 2005 server.
I plan to implement log shipping between the two servers. Do I have to restore using NO RECOVERY? I have read that I can not use STANDBY mode when restoring between 2005->2012. If so, is there a way to implement this without taking the
secondary sever offline?
Any other suggestions, on how to implement this?
Thanks.

Hi....
It should work for sure.. We have done exactly the same as you're proposing, log shipping from 2005 to 2012. Its always possible lower to higher but higher to lower is not possible.
Nothing will happen to SSRS.
Note : that we weren't using the SQL Server Log Shipping features, but our own custom scripts to do the backup/restore.
Please read the below links for more details and reference....
http://sqlblog.com/blogs/greg_low/archive/2011/01/12/log-shipping-between-versions-perhaps-2005-to-2008.aspx
http://msdn.microsoft.com/en-us/library/cc645954.aspx
http://msdn.microsoft.com/en-us/library/cc645954.aspx#KeepOldSecondaryAsNewPrimary
http://msdn.microsoft.com/en-us/library/cc645954.aspx#SwitchToOrigPrimary
http://redmondmag.com/articles/2010/06/28/log-shipping-logins-sql-server.aspx
http://sql-channel.com/2011/10/31/how-to-create-a-user-on-a-secondary-server-database-for-logshipping-in-standby-recovery-mode/
Regards
Raju R
Raju Rasagounder MSSQL DBA

DataBase Migration from SQL server 2005 to SQL server 2012

What are the challenges and steps to be taken care for proper migration of the Database.
Applications are using the Visual Studio 2012.
saikalyan

Few things that I can think of -
Verify all logins and users are migrated correctly.
Some of the SQL Server 2005 features/code could be deprecated in SQL Server 2012. Changes could be required before or after migration.
Some of the queries could have different performance (better or worse) on 2012 due to changes in query optimizer.
The applications/SSIS/DTS config files are updated to use the new server/instance name.
DNS alias names from the old servers (if used) are moved to the new server to have minimal impact on connection strings.
Plan for downtime of applications and batch processes.
Notify developers about the migration and the new server name(s)
- Aalam | (Blog)

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 & 2012

Similar Messages

Maybe you are looking for