SQL Server 2012 downgrade to SQL Server 2008

Hi, we purchased license for SQL Server 2012 recently. However, we realized that some of our existing softwares could not work well with SQL Server 2012. Are we still allowed to install SQL Server 2008 in this case? Thank you.

Hello Gan
see
http://download.microsoft.com/download/B/3/D/B3DE4C1D-5A2F-4DE4-ADAC-9209BF1A1B87/SQL-Server-2012-Licensing-Reference-Guide.pdf => Page 15 = Upgrades, Downgrades and Step-Ups
Anyway, you will have a problem to bring the databases back to 2008, because it's not possible to attach/restore a 2012 database to 2008 (R2).
Have you try to change the compatibility level of the database down to 2008, if the application works then?
Olaf Helper
* cogito ergo sum * errare humanum est * quote erat demonstrandum *
Wenn ich denke, ist das ein Fehler und das beweise ich täglich
Blog
Xing
Hi Olaf Helper,
Thank you for the documentation :) No worry, we are not downgrading the database yet. We are still at the development stage.
Regards,
Gan

Similar Messages

Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

Hi Bob，
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Msg 8631 Internal error: Server stack limit has been reached on SQL Server 2012 from T-SQL script that runs on SQL Server 2008 R2

I have an Script mostly that is generated by SSMS which works with-out issue on SQL Server 2008, but when I attempt to run it on a new fresh install of SQL Server 2012 I get an Msg 8631. Internal error: Server stack limit has been reached. Please look for
potentially deep nesting in your query, and try to simplify it.
The script itself doesn't seem to be all that deep or nested. The script is large 2600 lines and when I remove the bulk of the 2600 lines, it does run on SQL Server 2012. I'm just really baffled why something that SQL Server generated with very
few additions/changes AND that WORKS without issue in SQL Server 2008 R2 would suddenly be invalid in SQL Server 2012
I need to know why my script which is working great on our current SQL Server 2008 R2 servers suddenly fails and won't run on an new SQL Server 2012 server. This script is used to create 'bulk' Replications on a large number of DBs saving a tremendous
amount of our time doing it the manual way.
Below is an 'condensed' version of the script which fails. I have removed around 2550 lines of specific sp_addarticle statements which are mostly just copy and pasted from what SQL Management Studio 'scripted' for me went I when through the Replication
Wizard and told it to save to script.
declare @dbname varchar(MAX), @SQL nvarchar(MAX)
declare c_dblist cursor for
select name from sys.databases WHERE name like 'dbone[_]%' order by name;
open c_dblist
fetch next from c_dblist into @dbname
while @@fetch_status = 0
begin
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 2400 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script =
null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509F, @identityrangemanagementoption = N''manual'', @destination_table = N''TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false'', @ins_cmd = N''CALL sp_MSins_dboTABLE_ONE'',
@del_cmd = N''CALL sp_MSdel_dboTABLE_ONE'', @upd_cmd = N''SCALL sp_MSupd_dboTABLE_ONE''
EXEC sp_executesql @SQL
SET @dbname = REPLACE(@dbname, 'dbone_', 'dbtwo_');
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 140 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''DB_TWO_TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''DB_TWO_TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script
= null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509D, @identityrangemanagementoption = N''manual'', @destination_table = N''DB_TWO_TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false''
EXEC sp_executesql @SQL
fetch next from c_dblist into @dbname
end
close c_dblist
deallocate c_dblist
George P Botuwell, Programmer

Hi George,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
If you have any feedback on our support, please click
here.
Allen Li
TechNet Community Support

Using SSDT-BI in Visual Studio 2012 to create and maintain SSRS, SSAS, SSIS in SQL Server 2008 R2

Hi, My management is wanting all the developers (database and .net) to upgrade from Visual Studio 2008 to Visual Studio 2012. We are currently using SQL Server 2008 R2 for our data warehouse and using Business Intelligence (SSIS,
SSAS, and SSRS) to maintain it. Our database team is also wanting to create database projects and include that in our Team Foundation Server 2010 code repository along with our BI code. From what I've been able to research googling the
internet is there are two products available SSDT and SSDT-BI which can be installed into VS2012, but it appears that only SSDT for database projects is the only thing that will work until we someday upgrade to SQL Server 2012. Most of the information
I've found on the internet regarding this subject is over a year old and a lot can change in a year. So my questions are can we install VS2012 and both SSDT and SSDT-BI to create and maintain the SSIS, SSRS, and SSAS currently in our SQL Server 2008
R2 database? If we can install these three items, VS2012 and the two SSDTs, and are able to create new BI and maintain our current BI in our SS2008R2 database then what issues might we have with our TFS2010 code repository? We prefer
to use only VS2012 or VS2008 but not both at the same time. If we can't do everything we are currently doing in VS2008 with our SS2008R2 database by switching to VS2012 and the two SSDTs then we will stay with VS2008 until we someday upgrade
to SS2012. Please advise and thank you. James M.

I'm going to move this to the SSAS blog, where most SSDT-BI questions are answered (this forum mainly answers SSDT questions). Someone there may be able to give you better information but here's what I know:
- I think you'll only need to install SSDT-BI since you're using SSIS, SSAS and SSRS. SSDT is the database tooling which it sounds like you wouldn't use, and it's actually built into VS2012 in any case.
- SSIS projects don't work with earlier versions of SQL Server, but SSAS and SSRS do. Details are on
this blog post. I don't have enough knowledge to suggest workarounds or best practices for handling the SSIS issue. Perhaps you could keep 2 projects, or 2 branches of the same project (one for 2012, one for 2008) if that's possible? I think your BIDS projects
will be upgraded to SSDT-BI compatible projects so it's work checking them into source control, upgrading, then comparing to understand what's changed. You might be able to keep the same overall source and just change a few settings in the different branches?
Hopefully someone on the SSAS forum can help give you more information and suggestions.
Kevin

Update error of SQL Server 2012 enterprise running on Windows server 2008 standard SP2 (32 bits)

Hi there;
I have a windows server 2008 SP2 (32bits) in which I have an instance of SQL Server
2008 and another of 2012.
My Windows server 2008 installed the following updates; (see below).
(KB2898858),(KB2909921),(KB890830),(KB2898869),(KB2911502),(KB2901126),
(KB2916036),(KB2862973),(KB2901113)
After the machine was re-started, I was not abble to connect
to the instance of SQL Server 2012. I am able
to connect to the instance of SQL Server 2008.
The error message I get when I atemp to connect can be found
at the end of the list of updates below.
Do I need to uninstall an update? if so, which one and how do I do that?
Thanks Gabriel I. Ruiz
Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Vista SP2 and Windows Server 2008 SP2 x86 (KB2898858)
Installation date: ‎2/‎12/‎2014 11:42 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2898858
Cumulative Security Update for Internet Explorer 9 for Windows Server 2008 (KB2909921)
Installation date: ‎2/‎12/‎2014 11:42 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2909921
Windows Malicious Software Removal Tool - February 2014 (KB890830)
Installation date: ‎2/‎12/‎2014 11:41 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/890830
Security Update for Microsoft .NET Framework 4.5.1 on Windows 7, Windows Vista and Windows Server 2008 x86 (KB2898869)
Installation date: ‎2/‎12/‎2014 11:40 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2898869
Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Vista SP2 and Windows Server 2008 SP2 x86 (KB2911502)
Installation date: ‎2/‎12/‎2014 11:36 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2911502
Security Update for Microsoft .NET Framework 4.5.1 on Windows 7, Windows Vista, and Windows Server 2008 x86 (KB2901126)
Installation date: ‎2/‎12/‎2014 11:36 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2901126
Security Update for Windows Server 2008 (KB2916036)
Installation date: ‎2/‎12/‎2014 11:34 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2916036
Security Update for Windows Server 2008 (KB2862973)
Installation date: ‎2/‎12/‎2014 11:34 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2862973
Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Vista SP2 and Windows Server 2008 SP2 x86 (KB2901113)
Installation date: ‎2/‎12/‎2014 11:34 PM
Installation status: Successful
Update type: Important
More information:
http://support.microsoft.com/kb/2901113
===================================
Cannot connect to HAVANA\HAVANA_2012_1ST.
===================================
The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy
to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
Server Name: HAVANA\HAVANA_2012_1ST
Error Number: 233
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle, SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean callerHasConnectionLock)
at System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean canAccumulate)
at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode, Boolean canAccumulate)
at System.Data.SqlClient.TdsParser.SendPreLoginHandshake(Byte[] instanceName, Boolean encrypt)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
No process is on the other end of the pipe

Hi,
Check if SQL Server service is running fine. I doubt you may have changed the user account password used for SQL Server service. After restarting the machine, you also need to update the user account of SQL Server service in Configuration
Manager. Re-type the user account name and password under Log on tab and see how it helps.
Thanks.
Tracy Cai
TechNet Community Support

Attempted to perform an unauthorized operation error while installing SQL Server 2008 R2 Enterprise edition on Windows Server 2012 R2 standard VM server

I've been trying fresh installation of SQL Server 2008 R2 enterprise on Windows Server 2012 R2 standard VM server several times for two weeks, but always get the error "Attempted to perform an unauthorized operation". At first, I attempted
to install all features, but failed several times. So I decided to try install just Database Engine service, and still fail at the SqlBrowserConfigAction_Install_ConfigNonRC_Cpu32, with the error "Attempted to perform an unauthorized operation".
I remote login to server with my admin domain account. This account is in server local Administrators group. I
1. Right-click on setup.exe file | properties | Compatibility tab | select compatibility to Windows 8.Then click OK.
2. Right-click on setup.exe file | Run as Administrator, to start the Installation Center.
I have the document of my installation steps and zip file of the installation logs, if you need to take a look.
Appreciate for any help!
ntth

Hi ntth,
"Attempted to perform an unauthorized operation"
The above error is always related to the Windows account SID mapping. I recommend you login into Windows using another Windows account which has administrative privileges and run SQL Server setup using that Windows account.
Besides, please note that we need to apply SQL Server 2008 R2 Service Pack 2 or a later update when installing SQL Server Windows Server 2012 R2. For more information, please review this
KB article.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Difference between database features - SQL Server 2008 R2 navtive vs SQL Server 2012 with SQL Server 2008 compatibility set?

I am investigating the impact of upgrading from SQL Server 2008 R2 to SQL Server 2012. To reduce the impact of the upgrade, I am planning to restore / create our application database onto SQL Server 2012 with compatibility level 100 (SQL Server 2008 and
SQL Server 2008 R2).
Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?

Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?
Yes there can be difference and impact there are few features deprecated in SQL Server 2012 you must be aware about that. Please see
Deprecated Database Features in SQL Server 2012
Deprecated SQL Server features in SQL Server 2012
After you migrate database to 2012 please don't move ahead with production unless you have tested your application to new created database
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

SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

I am working in a Product based company.
We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
I have used "Script Component" in my package.
We will take only DTSX package file to the customer places and run using SQL Agent Job daily.
Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
Who are all(Customer Environments) using SQL 2012, I am facing the below issue
The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Still the same package is running fine for some of the customers having SQL 2012.
I am getting the above error only for few customers.
Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

Hi Katherine,
I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
Here is my Simple .net code
/* Microsoft SQL Server Integration Services Script Component
* Write scripts using Microsoft Visual C# 2008.
* ScriptMain is the entry point class of the script.*/
using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
public override void PreExecute()
base.PreExecute();
Add your code here for preprocessing or remove if not needed
public override void PostExecute()
base.PostExecute();
Add your code here for postprocessing or remove if not needed
You can set read/write variables here, for example:
Variables.MyIntVar = 100
int counter = 0;
public override void Input0_ProcessInputRow(Input0Buffer Row)
if (counter == 0)
counter = Convert.ToInt32(Row.JurisCount);
Row.JurisKey = counter;
counter = counter + 1;
PAVAN MSBI

SSIS 2012 package scheduling with SQL Server 2008 R2

Hi, We have a ssis 2012 package with parameters & would like to schedule this package in SQL Server 2008 R2 agent. Is there a way to pass parameters to the ssis package from SQL Server 2008 R2 agent?
Thanks in advance..........
Ione

You cant use SQL 2008 R2 to schedule it as dtexec 2008 cant execute package created using SSIS 2012. The inverse can be done though
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Will Report Builder 2012 Work with SQL Server 2008???

Simple question really
Will Report Builder 2012 work in conjunction with SQL Server 2008???
Is it worth while upgrading?
The main reason i ask is the ability to export in an xlsx format
Thanks

Hi Gmach,
The version of Report Builder on SQL Server Reporting Service (SSRS) 2012 is Report Builder 3.0. The Report Builder 3.0 manufactures 2010 RDL reports, so it only works with the version of SQL Server 2008 R2 or later. So in your scenario, we can no connect
to SQL Server 2008 Server using Report Builder that on SSRS 2012.
If you have any questions, please feel free to ask.
Regards,
Charlie Liao
TechNet Community Support

Install SQL Server 2008 R2 SP 1 on Windows Server 2012

Dear All,
I've downloaded SQL Server SP1 from this link:
http://www.microsoft.com/en-us/download/details.aspx?id=26727
I downloaded :
SQLServer2008R2SP1-KB2528583-x64-ENU.exe
SQLManagementStudio_x64_ENU.exe
SQLServer2008R2SP1-KB2528583-IA64-ENU.exe
when i run SQLServer2008R2SP1-KB2528583-x64-ENU.exe i have error:
There are no SQL Server instances or shared features that can be updated on this computer
what that i missed? is that i must install SQL Server 2008 R2?
because if i run the SQL Server 2008 R2 there are compatible issue. I run this on Windows Server 2012
Please Help.
Best regards,
Surbakti

Hi,
The cause could be an invalid entry in the userSettings section of the Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings file.
Delete this configuartion file or delete the folder "Microsoft_Corporation" and see how it works.
Run the command: rd /s /q %localappdata%\Microsoft_Corporation
For your reference:
http://blogs.msdn.com/b/smondal/archive/2013/07/26/an-error-occurred-creating-the-configuration-section-handler-for-usersettings-microsoft-sqlserver-configuration-landingpage-properties-settings.aspx
Thanks.
Tracy Cai
TechNet Community Support

WSUS 3.2 on Server 2008 R2 with SQL 2012 STD

Hi
I have a Windows 2008 Server R2 with SQL server 2012 STD on it, his is a VM(hyper v) and not connected to the internet machine.
I want to install the WSUS Role on it an it fails every time..
When installing the Role it fails with this error:
"he update could not be found. there may be a network connection issue."
I tried installing it using the installation .exe from Microsoft website
and also faild with this message:
"Windows server upate services 3.0 sp2 setup cannot continue. please resolve the following issues, and the run the setup again.Internet Information Services (IIS) or additional IIS role service
must be installed.
please refer to windows server update services 3.0 sp2 release notes for more information about prerequisites"
I must point that IIS IS INSTALLED and running on this server.
Does anyone knows how to solve this problem?
Thank you!!

I want to install the WSUS Role on it an it fails every time..
While not directly related to your situation, it's important to note that SQL2012 is
not a supported platform for WSUS v3.2. Be sure to install with the Windows Internal Database instead.
When installing the Role it fails with this error:
"The update could not be found. there may be a network connection issue."
The key here is in understanding HOW the WSUS role gets installed on a Server 2008 R2 system. The binaries used to install the role are NOT present on the OS image, they must be either downloaded from the Internet or obtained from another WSUS server with
the Dynamic Installer approved.
My guess would be that this system does not have Internet access. If you don't have another operational WSUS server, then this system will need to have Internet access to download the required binaries from MU, or else you'll need to download the standalone
installer and install it manually.
I tried installing it using the installation .exe from Microsoft website and also faild with this message:
"Windows server upate services 3.0 sp2 setup cannot continue. please resolve the following issues, and the run the setup again. Internet Information Services (IIS)
or additional IIS role service must be installed.
I must point that IIS IS INSTALLED and running on this server.
Ahhh.. was it previously installed for some other application. Have you *verified* that it is installed in a configuration that is compatible with WSUS?
HINT: WSUS is, fundamentally, an IIS6/ASP.NET v2 application. My first guess would be that your existing installation of IIS7.5 does not have the IIS6 components enabled.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

SQL Server 2008/2012 Express Connection Problem

Hello,
since a couple of days I'm working on a problem with the SQL Server Express (32-Bit as well as 64Bit).
I installed a new SQL Server 2008 with an instance named SQL2012 and the Management Studio 2008 R2 on the same machine. I easily am abled to connect to the Server using the Management Studio with several Server Name settings (localhost, IP, (local), .\SQL2012).
Now I have a self-written programm (C#) wich should connect to the Server, but it does not work. It is definitely not a problem of the programm code because the same programm is abled to connect to a SQL Server 2008 Enterprise Edition. Similar Problem with
the 2012 Express Version (2012 Enterprise not tested).
The connection string I use and wich is working with connecting on the Enterprise Edition is: Server=Servername\Instance;Database=DatabaseName;User Id=user;Password=password;
Anybody any solution why the Express-Version refuses to connect?
(Sorry if I have made several failures in my text, English is not my native language)

It Occurs when I try to ping.Send the Server to see if he is active. If I skip this step and try to connect directly to the server (con.Open()) I get the exception:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The
server was not found or it can not be accessed. Verify that the instance name is correct and that SQL Server allows remote connections. (provider: Named Pipes Provider, error: 40 - Connection with the SQL Server couldn't be opened)

SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

Hi All,
I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
Below is the screenshot for the same.
So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Again i still see the same above errors and with that a new error related to a MOF File.
Below are the contents of the error logs. Can some one assist on this issue.
======================================================
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052692
Exit facility code: 1212
Exit error code: 1324
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2015-01-15 13:53:03
End time: 2015-01-15 14:04:29
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: D:\SQLServer2008R2_SP1\x64\setup\
Installation edition: ENTERPRISE
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: E2KLAB\SCOMAC
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: D:\SQLServer2008R2_SP1\SP
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: E2KLAB\SCOMAC
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: E2KLAB\SCOMAC
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
MSI error description: The folder path 'Program Files' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
Gautam.75801

Hi Alberto,
Still the same issue.
I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and repaired the .NET using the .NET Repair tool
Also changed the installation directory to D:\ Drive this time. Still same issue.
log file:
===============
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052692
Exit facility code: 1212
Exit error code: 1324
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2015-01-15 22:55:37
End time: 2015-01-15 23:07:32
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: D:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
Any other suggestion i can try ?
Gautam.75801

Install SQL Server 2008 R2 in Windows Server 2012 using SQL4SAP Script

Hi guys,
Since we are performing a SAP System Migration from older releases of Windows/SQL Server, as detailed on SAP Note
1780433 - System copy of SAP systems on Windows 2012 : SQL Server
We need to install SQL Server 2008 R2 before upgrading the system
When running SQL4SAP Script it states the following
17/03/2014 08:13:44 p.m.
Message Box "Windows version error"
OS Family "WindowsNT6.3" is not supported by this script.
Result: vbOK
On Windows 2012 should i run the SETUP instead the script?
Thanks!

Hi Sunny
Im following SAP Note 1780433 - System copy of SAP systems on Windows 2012 : SQL Server
in order to migrate a SAP 640 system from Windows 2003/SQL Server 2005 to Windows 2012/ SQL Server 2012
Reason and Prerequisites
This note describes how to migrate the mentioned SAP products to Windows 2012/SQL Server 2008 R2,
in order to prepare an upgrade to SAP releases based on NW 7.0 and higher.
Note, that only SAP upgrade paths are supported, that are supported by the SUM tool. For more
information about the upgrade paths supported by SUM, read the Central SUM Note referred to at
http://www.service.sap.com/SLToolset.
Immediately after the SAP upgrade, your database has to be upgraded to SQL Server 2012. SAP does in general not support SQL Server releases prior to SQL Server 2012 on Windows 2012.
I understand this is not supported from Productive system, we are performing this on a Development system for test purposes.
Nevertheless on the note says Install First SQL Server 2008 R2 and after SAP upgrade, perform upgrade of SQL Server Upgrade, so there is misleasing information.
Im not sure if a 640 System would be able to copied and upgraded in Windows 2012/SQL Server 2012
It doesnt mention that 640_EX2 Kernel Support SQL Server 2012 to install the system.
How would yo recommend a system copy restoring database on these conditions?
640 System (SQL Server 2005,Win 2003) --> 640 System (SQL Server 2012, Win 2012)
(and then Upgrading to 740)
Thanks

SQL Server 2012 downgrade to SQL Server 2008

Similar Messages

Maybe you are looking for