May 23, 2011 at 7:43 am
mulle-78 (5/23/2011)
We could at the moment not solve the problem. What is with a fresh installation. Can uninstall the old MSSQL components, do a freh install of a named instance and attach the production database??
Yes you could do that.
What I have to do if I attach a MSSQL 2005 database to a MSSQL 2008 instance? Do I have to do some post activities on the customer DB?
Don't you want to use the upgrade advisor?
You could attach the Database and set the compatibility level.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
May 23, 2011 at 8:51 am
thx.. I will try this if enything else failes: http://msdn.microsoft.com/en-us/library/ms189625.aspx
I'm playing at the moment with the implicit_transactions setting:
http://msdn.microsoft.com/en-us/library/ms189631.aspx > user options (http://msdn.microsoft.com/en-us/library/ms176031.aspx)
for further ideas with trace flag -T3601; the upgrade script seems to have a problem with RECONFIGURE ??? :
/**************************************************************/
/* DMF Post-upgrade steps */
/**************************************************************/
--
-- >>> CTP5 -> CTP6 Upgrade
--
-- Restoring previously saved data and converting TargetSets to ObjectSets
IF (OBJECT_ID('dbo.dmf_upgrade', 'U') IS NOT NULL)
BEGIN
BEGIN TRANSACTION
-- Restore policies
SET IDENTITY_INSERT dbo.syspolicy_policies_internal ON
INSERT dbo.syspolicy_policies_internal (policy_id,name,condition_id,root_condition_id,date_created,execution_mode,policy_category_id,schedule_uid,description,help_text,help_link,is_enabled,job_id,created_by,modified_by,date_modified)
SELECT policy_id,name,condition_id,root_condition_id,date_created,execution_mode,policy_category_id,schedule_uid,description,help_text,help_link,is_enabled,job_id,created_by,modified_by,date_modified
FROM msdb.dbo.tmp_syspolicy_policies_internal
SET IDENTITY_INSERT dbo.syspolicy_policies_internal OFF
-- Restore Health state
SET IDENTITY_INSERT dbo.syspolicy_system_health_state_internal ON
INSERT dbo.syspolicy_system_health_state_internal (health_state_id,policy_id,last_run_date,target_query_expression_with_id,target_query_expression,result)
SELECT * FROM msdb.dbo.tmp_syspolicy_system_health_state_internal
SET IDENTITY_INSERT dbo.syspolicy_system_health_state_internal OFF
-- Restore Execution history
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_internal ON
INSERT dbo.syspolicy_policy_execution_history_internal (history_id,policy_id,start_date,end_date,result,is_full_run,exception_message,exception)
SELECT * FROM msdb.dbo.tmp_syspolicy_policy_execution_history_internal
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_internal OFF
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_details_internal ON
INSERT dbo.syspolicy_policy_execution_history_details_internal (detail_id,history_id,target_query_expression,target_query...
2011-05-23 14:03:53.29 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2011-05-23 14:03:53.29 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2011-05-23 14:03:53.30 spid7s Error: 574, Severity: 16, State: 0.
2011-05-23 14:03:53.30 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-23 14:03:53.30 spid7s Error: 912, Severity: 21, State: 2.
May 24, 2011 at 4:01 am
implicit transactions is not active, user options is '0', is this correct?
http://connect.microsoft.com/SQLServer/feedback/details/616796/sql-2008-sp1-fails-to-install
further error details:
2011-05-23 15:49:27.21 spid7s Error: 15002, Severity: 16, State: 1.
2011-05-23 15:49:27.21 spid7s The procedure 'sys.sp_dbcmptlevel' cannot be executed within a transaction.
2011-05-23 15:49:27.22 spid7s Error: 266, Severity: 16, State: 2.
2011-05-23 15:49:27.22 spid7s Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.
2011-05-23 15:49:27.22 spid7s Executing batch :
-- Allow updates to system catalogs so that we can fully manipulate our system objects
EXECUTE master.dbo.sp_configure N'allow updates', 1
2011-05-23 15:49:27.41 spid7s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-05-23 15:49:27.41 spid7s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-05-23 15:49:27.41 spid7s Executing batch :
RECONFIGURE WITH OVERRIDE
2011-05-23 15:49:27.42 spid7s Error: 574, Severity: 16, State: 0.
2011-05-23 15:49:27.42 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-23 15:49:27.58 spid7s Error: 912, Severity: 21, State: 2.
2011-05-23 15:49:27.58 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2011-05-23 15:49:27.60 spid7s Error: 3417, Severity: 21, State: 3.
2011-05-23 15:49:27.60 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2011-05-23 15:49:27.60 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2011-05-23 15:49:27.69 Server The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/TPZSQP01.ICOTPZ.local:SAPQPT ] for the SQL Server service.
2011-05-23 15:49:27.69 Server The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/TPZSQP01.ICOTPZ.local:54405 ] for the SQL Server service.
August 16, 2011 at 6:30 am
==>
Enable trace flag 902 on the instance of SQL Server 2008 R2. To do this, follow these steps:
Open SQL Server Configuration Manager.
In SQL Server Configuration Manager, click SQL Server Services.
Double-click the SQL Serverservice.
In the SQL Server Properties dialog box, click the Advanced tab.
On click the Advanced tab, locate the Startup Parameters item.
Add ;-T902 to the end of the existing string value, and then click OK.
Right-click the SQL Serverservice, and then click Start.
If the SQL Server Agent service is running, right-click the SQL Server Agent service, and then click Stop.
Open SQL Server Management Studio, and then connect to the instance of SQL Server 2008 R2.
Run the following statements:
EXEC sp_configure 'show advanced', 1;
RECONFIGURE;
EXEC sp_configure 'allow updates', 0;
RECONFIGURE;
EXEC sp_configure 'Agent XPs', 1;
RECONFIGURE;
GO
In SQL Server Configuration Manager, right-click the SQL Serverservice, and then click Stop.
Remove trace flag 902 on the instance of SQL Server 2008 R2. To do this, delete ;-T902 from the string value that you updated in step 1f.
Right-click the SQL Serverservice, and then click Start.
Right-click the SQL Server Agent service, and then click Start.
In SQL Server Management Studio, reconnect to the instance of SQL Server 2008 R2.
In Object Explorer, expand Management, right-click Data Collection, and then click Enable Data Collection.
Note If data collection is already enabled, the Enable Data Collection item is unavailable
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply