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/

Similar Messages

SQL Server reporting server 2005 having error. 'The report server is not responding. Verify that report server is running and can be accessed from this computer'

Hi team,
I got below error message in SQL Server 2005 reporting service.
''The report server is not responding. Verify that report server is running and can be accessed from this computer'
also in reports, i am getting below error:
"The encrypted value for the "LogonCred" configuration setting cannot be decrypted. (rsFailedToDecryptConfigInformation)
Get Online Help
The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)
Get Online Help "
Please find below log:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.4060.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Daylight Time</TimeZone>
<Path>F:\Program Files\Microsoft SQL Server\MSSQL.6\Reporting Services\LogFiles\ReportServer__07_28_2014_09_08_41.log</Path>
<SystemName>MFLDDDBS04</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 2</OSName>
<OSVersion>5.2.3790.131072</OSVersion>
</Header>
w3wp!webserver!1!7/28/2014-09:08:41:: i INFO: Reporting Web Server started
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing ConnectionType to '1' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration
file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
w3wp!resourceutilities!1!7/28/2014-09:08:42:: i INFO: Reporting Services starting SKU: Enterprise
w3wp!resourceutilities!1!7/28/2014-09:08:42:: i INFO: Evaluation copy: 0 days left
w3wp!library!1!7/28/2014-09:08:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information., CryptUnprotectData:
Win32 error:13;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
w3wp!library!1!7/28/2014-09:08:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the report server log files for more information.
   at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.UnprotectData(Byte[] data, Int32 dwFlags, Boolean transitoryData)
   at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.LocalUnprotectData(String data, Boolean transitoryData)
   at Microsoft.ReportingServices.Diagnostics.RSConfiguration.DecryptCatalogData(String encryptedData, String element)
   --- End of inner exception stack trace ---

Hi Vivek,
In Reporting Services, values for LogonUser, LogonDomain, and LogonCred are created when the report server connection is configured to use a domain account. As to the error that “The encrypted value for the "LogonCred" configuration setting cannot be decrypted”,
we can know that it relates to the domain account for report server connection.
To fix this issue, we can refer to the following steps:
Log in to SQL Server Database Engine in SQL Server Management Studio.
Under Security folder, give sufficient permissions for your domain account.
Open your Reporting Services Configuration (go to Start -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> Reporting Services Configuration)
Navigate to the Database Setup tab, select ‘Service Credentials’ as the Credentials Type, then type your domain account and password in there. Press Apply.
Restart the Report Server services.
Reference:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2d05b404-83aa-4fb2-bba6-52b587e890ec/sql-2005-rs-configuration-tool-encryption-key-error
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Regarding ReCreating Catalog in SQL Server 2005 which was existing in SQL Server 2000

Hello
I was using SQL SERVER 2000 ... In one table I've created FULL TEXT SEARCHING ( Full text catalog along with full text indexing)
Now we had to install our db in SQL SERVER 2005 standard edition. But while taking script it gave me two lines like:
if (select DATABASEPROPERTY(DB_NAME(), N'IsFullTextEnabled')) <> 1
exec sp_fulltext_database N'enable'
GO
if not exists (select * from dbo.sysfulltextcatalogs where name = N'DEV_CAS_DiagnosisCatalog')
exec sp_fulltext_catalog N'DEV_CAS_DiagnosisCatalog', N'create'
GO
so I used this in the new db creation script...
But I couldn't get where it actually is in SQL SERVER 2005 standard edition.
and also plz help how should we create if it doesn't exist...
What could be the problem....
Thanks In advance

if (select DATABASEPROPERTY(DB_NAME(), N'IsFullTextEnabled')) <> 1
exec sp_fulltext_database N'enable'
GO
if not exists (select * from dbo.sysfulltextcatalogs where name = N'DEV_CAS_DiagnosisCatalog')
exec sp_fulltext_catalog N'DEV_CAS_DiagnosisCatalog', N'create'
GO
sp_fulltext_catalog [ @ftcat= ] 'fulltext_catalog_name' ,
[ @action= ] 'action'
[ , [ @path= ] 'root_directory' ]
Full-text catalog and index data is stored in files created in a full-text catalog directory(not on SSMS). The full-text catalog directory is created as a sub-directory of the directory specified in
@path or in the server default full-text catalog directory if
@path is not specified. The name of the full-text catalog directory is built in a way that guarantees it will be unique on the server. Therefore, all full-text catalog directories on a server can share the same path.
Refer the path column by running the below query. full text catalog file is created under the root directory by default if the path is not specified.
select * from dbo.sysfulltextcatalogs where name = N'DEV_CAS_DiagnosisCatalog'
Refer
http://technet.microsoft.com/en-us/library/ms189520(v=sql.90).aspx
Regards, RSingh

Package developed on SQL Server 2005 SP1 not opening in SQL Server 2005 SP2

Recently I have upgraded my system to SQL Server 2005 SP2 version 9.00.3054; I have developed my packages on SQL Server 2005 SP1 version 9.00.2047. I am unable to open all these packages on SQL Serever SP2 version 9.00.3054 it is giving me error.
Error: Error loading Package.dtsx cannot create an instance of the XML Document Object Model. MSXML may not be registered.
Can any body help me in this?
Thanks in advance

Try the search function.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1446338&SiteID=1

Upgrade to SQL server 2005 - Point Production Environment to New Server?

We have Essbase, Workspace, EAS, EIS, FR, WA environment in Production, supporting SQL server databases are on ServerA which has all these databases in SQL server 2000. The corporate standard is moving to SQL server 2005, and the SQL server DBA has copied the supporting dbs to ServerB for testing.
Is "pointing" to ServerB an option, or do the BI+ components have to be redeployed? Any help or pointing in the right direction would be appreciated.

Stephanie,
There could be schema changes between 2000 and 2005 you may want to check the support matrix to ensure your version of Hyperion is supported with SQL 2005.
Best bet is to back up the business rules, fr reports and then configure the system to the new databases on the SQL 2005 box then reimport the items.
JTS

Upgrading from SQL Server 2005 Compact Edition [ENU] to SQL Server 2008 Express Edition OR HIGHER for Microsoft Security Compliance Manager

I have downloaded the MS Security Compliance Manager, which is in two parts: MS SQL Server 2008 Express Edition & the SCM. The install instructions state the the server needs to be install before the SCM. So as the install continues I get
an error message, which cancels the installation. So, I am trying to install SQL 2008 EE separate from SCM. My question is:
Can I upgrade from my current SQL Server 2005 Compact Edition [ENU]
directly to SQL Server 2008 Express Edition (or higher)?

So as the install continues I get an error message, which cancels the installation.
And which error message did you got?
SQL Server Compact Edition is something different then SQL Server Express (or Standard) Edition, you can't upgrade it as you asked for,.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Replacing a SQL Server 2005 Express Database with a SQL CE 3.5 database

I am just googling for the past few days to find out the answer to this problem..
I have an app developed over few man-years of effort - with vb.net and SQL 2005 Express Db. Now we use VS 2010 sp1 with .net 3.5 sp1. We have used plain T-SQL commands and the app was performing admirably well. The DB has about forty tables. The data
volume is about 200 to 300 mb max - but mainly it stays about 50 to 60 mb in many places. We are also using XML data transfers to backup the data.
Now we want to shift to SQL CE 3.5 or 4.0 - just to avoid the pain of SQL Express download and installation by the users. We have successfully created a 3.5 and 4.0 sdf files. But when we change the connection from a mdf file to the sdf file in the VS2010 settings
area, it just goes fine - the connection string is accepted and the app starts. But we get the usual error no 26 - unable to locate the database file - and a five line message that it is not able to connect to the sql server.
Are we missing something ? We have included the sqlce dll in the references.. but just not able to make the app connect to the sdf file..
All the codes, datasets, adapters, queries are just intact in the app - but just we are not able to connect to the sdf database.
We would appreciate help in this regard and also in doing a build with SQL Ce with Inno Setup which we have been using so long.
Finally there is too much of SQL CEs around - but 3.5, 3.5 sp2 and now CE 4.0 seems to be ones to go in for. Which one is really the best for our app - 3.5 or 4.0 ?
Thanks in advance.

we change the connection from a mdf file to the sdf file ... All the codes, datasets, adapters, queries are just intact in the app...
Agree with Erik, just changing the connection string don't work, you have to use data access components from
System.Data.SqlServerCe Namespace instead of
System.Data.SqlClient Namespace
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL Server 2005 SP4 not installing correct on Server 2003

Everytime I attempt to install SP4 on my Server 2003 system it states it goes through successfully but when I reboot it hasn't done anything.
Summary Log states all is successful for version 9.00.5000.00 (0 Errors, SQL Support: Passed, Summary: Successful)
after reboot or even before the sqlserver.exe shows its still version 9.00.4262.00 and still shows up in Microsoft updates and doesn't show the install at all in Add/Remove Programs
I'm at a complete loss on what to do.. I've tried the RTM download and the Auto Update method both with same results. Tried shutting down all services in relation as well. I'm lost

Time: 01/30/2015 14:24:13.797
KB Number: KB2463332
Machine: *CLEARED*
OS Version: Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 4
Package Version: 5000
Command-line parameters specified:
Cluster Installation: No
Prerequisites Check & Status
SQLSupport: Passed
Products Detected                         Language Level Patch Level       Platform Edition
Setup Support Files                       ENU
9.4.5000 x86
SQL Server Native Client                  ENU                 9.00.5000.00 x86
SQLXML4                                   ENU
9.00.5000.00 x86
Backward Compatibility                    ENU                    8.05.2312
x86
Microsoft SQL Server VSS Writer           ENU                 9.00.5000.00 x86
Products Disqualified & Reason
Product                                   Reason
Processes Locking Files
Process Name          Feature               Type          User Name
PID
Product Installation Status
Product                   : Setup Support Files
Product Version (Previous): 5000
Product Version (Final)   : 5000
Status                    : Success
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_SqlSupport.msi.log
Error Number              : 0
Error Description         :
Product                   : SQL Server Native Client
Product Version (Previous): 5000
Product Version (Final)   : 5000
Status                    : Success
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_sqlncli.msi.log
Error Number              : 0
Error Description         :
Product                   : SQLXML4
Product Version (Previous): 5000
Product Version (Final)   : 5000
Status                    : Success
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_sqlxml4.msi.log
Error Number              : 0
Error Description         :
Product                   : Backward Compatibility
Product Version (Previous): 2312
Product Version (Final)   : 2312
Status                    : Success
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_SQLServer2005_BC.msi.log
Error Number              : 0
Error Description         :
Product                   : Microsoft SQL Server VSS Writer
Product Version (Previous): 5000
Product Version (Final)   : 5000
Status                    : Success
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_SqlWriter.msi.log
Error Number              : 0
Error Description         :
Summary
     Success
     Exit Code Returned: 0

SQL Server 2005 upgrade & migrate to 2012 method

Hi,
The situation is like this:
Currently I have SQL Server 2005 on an old Windows Server 2003. The target is to let SQL Server 2012 on Windows Server 2012 with the databases migrated over. The new server with Windows Server 2012 was prepared.
Originally my plan is to install SQL Server 2005 on the new Windows Sever 2012 first, migrate the database from old server to here, then upgrade SQL Server to 2012. Then found out this method cannot be used due to SQL Server 2005 is not compatible with Windows
Server 2012.
Alternative suggestions are appreciated.

SQL Server 2012 supports upgrade from the following versions of SQL Server:
SQL Server 2005 SP4 or later
SQL Server 2008 SP2 or later
SQL Server 2008 R2 SP1 or late
So please make sure that your existing sql server 2005 is upgraded to SP4 or later.
Then best way is use side by side.
Windows Sever 2012 on you new machine and sql server 2012.
Then use side by side method to migrate your old sql 2005 to new version 2012, ( moving backups and restore, logins, jobs, packages, configurations, maintenance plans,
linked server details and more. )
If you use in-place the in case of any issues we cant do anything to bring back the server to old version or fixing the issue may take lot of time. side by side its matter of navigating the connection and changing the connection setting for application and
putting databases for use ( online from single user or may be from online to online )
Raju Rasagounder MSSQL DBA

How can I connect NetBeans 6.1 with SQL Server 2005?

Hello guys...
how can i connect NetBeans 6.1 with SQL Server 2005?
there is no SQL Server in Server list when we create a new Web Project and choose Server.
I'm new to NetBeans and this is my first time of posting.
If has some errors and unwanted disturbing,pls understand me. Thanks.
(If you have references or some snippets, i'll be glad if u can share.)
scsfdev

The JDBC-ODBC bridge wasn't recognizing any of the primary keys I had set up in SQL Server. After lots of head banging, here's the solution I came up with:
1. Download the appropriate driver. SQL Server 2000 requires the SQL Server 2000 JDBC driver (http://www.microsoft.com/downloads/details.aspx?FamilyId=07287B11-0502-461A-B138-2AA54BFDC03A&displaylang=en).
SQL Server 2005 download: (http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en)
3. After installing, right-click on "Libraries" in your project, and choose "Add Library...". Next, give it a name (i.e. SQLServer2000), and select "Class Libraries".
4. On the next screen, find the JAR files (should be in C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\), and add them under the "Classpath" tab. It will now be available under "Libraries" for future projects.
5. You can now create a connection to a specific database under the "Services" tab (next to "Projects" and "Files" in the top left of the screen). Select "Microsoft Sql Server 2000 (Microsoft Driver)" and format the "Database URL" like this:
jdbc:microsoft:sqlserver//YOURSERVER:1433;DatabaseName=YOURDATABASE
1433 is the default port, though your DBA may have changed it.
I posted a simpler version of this on the NetBeans.org FAQ page - they had the following title with no content on the answer page:
"Cannot Select Tables From MsSql 2000 Because It Says No Primary Key Next To Each Table But The Tables DO Have A Primary Key. What Do I Do?"

Sql Server 2005 schemas

Hi,
We have upgraded our database to Sql Server 2005 and now we can�t
run a query like this in our program:
SELECT * FROM tablename
If we change the query to this:
SELECT * FROM schema.tablename
then it works fine.
Do you have to specify the schema in the query or can you set this in
the datasource or connection or some other place?
The program must be able to run with a Oracle database to.
We use JBoss 4.0.2.
Thanks!

Hi,
We have upgraded our database to Sql Server 2005Sounds like a mistake.
and now we can�t
run a query It certainly was a mistake.
like this in our program:
SELECT * FROM tablename
If we change the query to this:
SELECT * FROM schema.tablename
then it works fine.
Roll back.
Do you have to specify the schema in the query or can
you set this in
the datasource or connection or some other place?
The program must be able to run with a Oracle
database to.
We use JBoss 4.0.2.
SQL Server 2005 made alot of subtle changes all over the place when it came to schemas and, permissions and how things are set up. After my own migration woes I came to the conclusion that SQL Server 2005 is just a "keep SQL Server DBA's employed" tool with no other features or benefits. The seemingly random poorly documented changes gave me night sweats.
In the end no, you should not have to specify schema, your connection and permissions are wrong. Your DBA should look into fixing this I guess.

How to find the list of unused stored procedures in SQL Server 2005?

Hi,
I need to find out the list of stored procedures which are not in use.
I found there is something called "sys.dm_exec_procedure_stats " for SQL server 2008.
Can you please suggest your ides here to do the same job for SQL server 2005.
Many Thanks.

In SQL 2005 there is, sort of. This is query lists the last execution
time for all SQL modules in a database:
SELECT object_name(m.object_id), MAX(qs.last_execution_time)
FROM sys.sql_modules m
LEFT JOIN (sys.dm_exec_query_stats qs
CROSS APPLY sys.dm_exec_sql_text (qs.sql_handle) st)
ON m.object_id = st.objectid
AND st.dbid = db_id()
GROUP BY object_name(m.object_id)
But there are tons of caveats. The starting point of this query is
the dynamic management view dm_exec_query_stats, and the contents is
per *query plan*. If a stored procedure contains several queries,
there are more than one entry for the procedure in dm_exec_query_stats.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

How to attached a sql server 2008 database on sql server 2005

Hi,
I have a backup of database designed over sql server 2008. I need to attacched this on a machine where sql server 2005 is installed and I am getting the message while attaching the database.
"The database can not be opened because it is version 661.
the server supports version 611 and earlier"

You need to install/have another instance of SQL Server 2008, restore over there the database and perhaps create a SSIS package to move objects and data into SQL Server 2005
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
"Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
Nor will the query execute; I get a transport-level error 0. Any thoughts?

Hi Davidmhjr,
>>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
More information about configuration requirement to run T-SQL debugger as below, please refer:
There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
any named instance.
•If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
Hope it is helpful.
Regards, Amber zhang

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

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

Similar Messages

Maybe you are looking for