Is it safe to delete "SystemCenterReporting" DB
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Is it safe to delete "SystemCenterReporting" DB

 
Post new topic   Reply to topic    Windows Server Forum Index -> MOM
Author Message
Andrew
Guest
Posted: Sat Jan 15, 2005 3:57 am    Post subject: Is it safe to delete "SystemCenterReporting" DB Reply with quote
I uninstalled MOM Reporting Server add on, it is safe to just delete the
entire DB using Enterprise Manager? Is there another way to my madness?
Back to top
James Morey
Guest
Posted: Sat Jan 15, 2005 4:03 am    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
The database remaining after uninstall of the MOM Reporting Components is
expected behavior. This is also true of the MOM Operations DB. The reason is
that you might want to preserve the DB and the data.

You can safely drop the DB using EM after uninstalling the Reporting
components.

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:265331D7-E3B7-4E15-A374-FCEF9CFC72CF@microsoft.com...
Quote:
I uninstalled MOM Reporting Server add on, it is safe to just delete the
entire DB using Enterprise Manager? Is there another way to my madness?
Back to top
JesseH
Guest
Posted: Sat Jan 15, 2005 4:38 am    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
Double check your grooming jobs on the OnePoint database and make SURE that
events are getting groomed out.

I did have a OnePoint database get REALLY big after I dropped a
SystemsCenterReporting DB...

"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23$bevTo%23EHA.3708@TK2MSFTNGP14.phx.gbl...
Quote:
The database remaining after uninstall of the MOM Reporting Components is
expected behavior. This is also true of the MOM Operations DB. The reason
is
that you might want to preserve the DB and the data.

You can safely drop the DB using EM after uninstalling the Reporting
components.

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:265331D7-E3B7-4E15-A374-FCEF9CFC72CF@microsoft.com...
I uninstalled MOM Reporting Server add on, it is safe to just delete the
entire DB using Enterprise Manager? Is there another way to my madness?

Back to top
James Morey
Guest
Posted: Sat Jan 15, 2005 4:45 am    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
The Reporting DTS job copies the operational data from the OnePoint DB to
the SystemCenterReporting DB daily. The OnePoint grooming jobs delete the
old data from the MOM Operational DB (OnePoint) daily.

"Theoretically" dropping the Reporting DB should not affect the OnePoint DB
much, but then again....

I'll look into this. Would be good to doc this somehow so folks are aware of
this affect.

Thanks

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"JesseH" <Jesse.Harris@Gmail.com> wrote in message
news:uToyLno%23EHA.3988@TK2MSFTNGP11.phx.gbl...
Quote:
Double check your grooming jobs on the OnePoint database and make SURE
that
events are getting groomed out.

I did have a OnePoint database get REALLY big after I dropped a
SystemsCenterReporting DB...

"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23$bevTo%23EHA.3708@TK2MSFTNGP14.phx.gbl...
The database remaining after uninstall of the MOM Reporting Components is
expected behavior. This is also true of the MOM Operations DB. The reason
is
that you might want to preserve the DB and the data.

You can safely drop the DB using EM after uninstalling the Reporting
components.

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:265331D7-E3B7-4E15-A374-FCEF9CFC72CF@microsoft.com...
I uninstalled MOM Reporting Server add on, it is safe to just delete the
entire DB using Enterprise Manager? Is there another way to my madness?



Back to top
JesseH
Guest
Posted: Sat Jan 15, 2005 5:23 am    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
Look at Select * from OnePoint..ReportingSettings

This will show you the TimeDTSLastRan.... All I know is I kept looking at
this table when My OnePoint Database started filling up.


"James Morey" <jmorey@online.microsoft.com> wrote in message
news:uUbZEro%23EHA.2788@TK2MSFTNGP15.phx.gbl...
Quote:
The Reporting DTS job copies the operational data from the OnePoint DB to
the SystemCenterReporting DB daily. The OnePoint grooming jobs delete the
old data from the MOM Operational DB (OnePoint) daily.

"Theoretically" dropping the Reporting DB should not affect the OnePoint
DB
much, but then again....

I'll look into this. Would be good to doc this somehow so folks are aware
of
this affect.

Thanks

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"JesseH" <Jesse.Harris@Gmail.com> wrote in message
news:uToyLno%23EHA.3988@TK2MSFTNGP11.phx.gbl...
Double check your grooming jobs on the OnePoint database and make SURE
that
events are getting groomed out.

I did have a OnePoint database get REALLY big after I dropped a
SystemsCenterReporting DB...

"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23$bevTo%23EHA.3708@TK2MSFTNGP14.phx.gbl...
The database remaining after uninstall of the MOM Reporting Components
is
expected behavior. This is also true of the MOM Operations DB. The
reason
is
that you might want to preserve the DB and the data.

You can safely drop the DB using EM after uninstalling the Reporting
components.

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:265331D7-E3B7-4E15-A374-FCEF9CFC72CF@microsoft.com...
I uninstalled MOM Reporting Server add on, it is safe to just delete
the
entire DB using Enterprise Manager? Is there another way to my
madness?





Back to top
Arie de Haan
Guest
Posted: Sat Jan 15, 2005 5:42 am    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
In article <uUbZEro#EHA.2788@TK2MSFTNGP15.phx.gbl>,
jmorey@online.microsoft.com says...
Quote:
The Reporting DTS job copies the operational data from the OnePoint DB to
the SystemCenterReporting DB daily. The OnePoint grooming jobs delete the
old data from the MOM Operational DB (OnePoint) daily.

"Theoretically" dropping the Reporting DB should not affect the OnePoint DB
much, but then again....

I'll look into this. Would be good to doc this somehow so folks are aware of
this affect.

Thanks


Grooming of the onepoint db wil be done when the DTS package has

succesfully run.

This is the setting after reporting is installed, but is it removed
after deinstalling reporting?
--
Greetz,

Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc.
Back to top
James Morey
Guest
Posted: Sat Jan 15, 2005 6:47 am    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
Hmmmm. Htis is a good one. I'll look into it and get back when I have
something.

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Arie de Haan" <com.pandinus@ariedh.reversed> wrote in message
news:MPG.1c527743543888ad989807@207.46.248.16...
Quote:
In article <uUbZEro#EHA.2788@TK2MSFTNGP15.phx.gbl>,
jmorey@online.microsoft.com says...
The Reporting DTS job copies the operational data from the OnePoint DB to
the SystemCenterReporting DB daily. The OnePoint grooming jobs delete the
old data from the MOM Operational DB (OnePoint) daily.

"Theoretically" dropping the Reporting DB should not affect the OnePoint
DB
much, but then again....

I'll look into this. Would be good to doc this somehow so folks are aware
of
this affect.

Thanks


Grooming of the onepoint db wil be done when the DTS package has
succesfully run.

This is the setting after reporting is installed, but is it removed
after deinstalling reporting?
--
Greetz,

Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc.
Back to top
Arie de Haan
Guest
Posted: Sat Jan 15, 2005 10:09 pm    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
In article <OTzEDvp#EHA.2016@TK2MSFTNGP15.phx.gbl>,
jmorey@online.microsoft.com says...
Quote:
Hmmmm. Htis is a good one. I'll look into it and get back when I have
something.


yeh, make a blog entry for this ;)

--
Greetz,

Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc.
Back to top
James Morey
Guest
Posted: Mon Jan 17, 2005 7:24 pm    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
Good suggestions ; )

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Arie de Haan" <com.pandinus@ariedh.reversed> wrote in message
news:MPG.1c535e9cfbaafa1d98980a@207.46.248.16...
Quote:
In article <OTzEDvp#EHA.2016@TK2MSFTNGP15.phx.gbl>,
jmorey@online.microsoft.com says...
Hmmmm. Htis is a good one. I'll look into it and get back when I have
something.


yeh, make a blog entry for this ;)
--
Greetz,

Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc.
Back to top
Gerrie
Guest
Posted: Tue Jan 18, 2005 3:29 pm    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
Grooming of your production database only occurs after the dts happened
"James Morey" wrote:

Quote:
Good suggestions ; )

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Arie de Haan" <com.pandinus@ariedh.reversed> wrote in message
news:MPG.1c535e9cfbaafa1d98980a@207.46.248.16...
In article <OTzEDvp#EHA.2016@TK2MSFTNGP15.phx.gbl>,
jmorey@online.microsoft.com says...
Hmmmm. Htis is a good one. I'll look into it and get back when I have
something.


yeh, make a blog entry for this ;)
--
Greetz,

Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc.



Back to top
James Morey
Guest
Posted: Wed Jan 19, 2005 12:58 am    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
I am doing some investigation into this and there *might* be a bug when
uninstalling Reporting. When you install Reporting it tells the MOM
operational DB to hold off on grooming until the DTS job finishes (so you
don't loose any reporting data).

The problem comes when you uninstall Reporting. Apparently (and we are still
looking into this) the uninstall misses something and the MOM DB keeps
waiting for the DTS to finish, which, of course, it never does because it
doesn't exist anymore.

You can still run the grooming jobs manually using SQL Server Enterprise
Manager.

I will forward any info I get on this.

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Gerrie" <Gerrie@discussions.microsoft.com> wrote in message
news:AD65A46B-75F0-4F64-A01C-22C492A5D95F@microsoft.com...
Quote:
Grooming of your production database only occurs after the dts happened
"James Morey" wrote:

Good suggestions ; )

--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================


"Arie de Haan" <com.pandinus@ariedh.reversed> wrote in message
news:MPG.1c535e9cfbaafa1d98980a@207.46.248.16...
In article <OTzEDvp#EHA.2016@TK2MSFTNGP15.phx.gbl>,
jmorey@online.microsoft.com says...
Hmmmm. Htis is a good one. I'll look into it and get back when I have
something.


yeh, make a blog entry for this ;)
--
Greetz,

Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc.



Back to top
Arie de Haan
Guest
Posted: Thu Jan 20, 2005 3:27 am    Post subject: Re: Is it safe to delete "SystemCenterReporting" DB Reply with quote
In article <265331D7-E3B7-4E15-A374-FCEF9CFC72CF@microsoft.com>,
Andrew@discussions.microsoft.com says...
Quote:
I uninstalled MOM Reporting Server add on, it is safe to just delete the
entire DB using Enterprise Manager? Is there another way to my madness?

After you uninstall the Reporting server add on, a table is still in the

OnePoint database which isn't updated anymore and therefor grooming will
not happen.
As James said MS is looking at this and i think we can expect a KB on it
pretty soon. But to get around it for now use 1 of 2 options:
1. - Dropping the table - put this in SQL Query analyzer and then press
F5:

USE ONEPOINT
drop table [ReportingSettings]
GO


2. - Updating the field in the ReportSettings table to fool the grooming
jobs - put this in SQL Query Analyzer and then press F5:
-- Script generated on 1/19/2005 11:01 AM
-- By: Arie de Haan
-- Server: (local)

BEGIN TRANSACTION
DECLARE @JobID BINARY(16)
DECLARE @ReturnCode INT
SELECT @ReturnCode = 0
IF (SELECT COUNT(*) FROM msdb.dbo.syscategories WHERE name =
N'[Uncategorized (Local)]') < 1
EXECUTE msdb.dbo.sp_add_category @name = N'[Uncategorized (Local)]'

-- Delete the job with the same name (if it exists)
SELECT @JobID = job_id
FROM msdb.dbo.sysjobs
WHERE (name = N'MOM Grooming fooling')
IF (@JobID IS NOT NULL)
BEGIN
-- Check if the job is a multi-server job
IF (EXISTS (SELECT *
FROM msdb.dbo.sysjobservers
WHERE (job_id = @JobID) AND (server_id <> 0)))
BEGIN
-- There is, so abort the script
RAISERROR (N'Unable to import job ''MOM Grooming fooling'' since
there is already a multi-server job with this name.', 16, 1)
GOTO QuitWithRollback
END
ELSE
-- Delete the [local] job
EXECUTE msdb.dbo.sp_delete_job @job_name = N'MOM Grooming fooling'
SELECT @JobID = NULL
END

BEGIN

-- Add the job
EXECUTE @ReturnCode = msdb.dbo.sp_add_job @job_id = @JobID OUTPUT ,
@job_name = N'MOM Grooming fooling', @owner_login_name = N'PANDINUS-LCL
\Administrator', @description = N'This is a job for fooling the MOM
Grooming job in thinking the reportingserver is still present',
@category_name = N'[Uncategorized (Local)]', @enabled = 1,
@notify_level_email = 0, @notify_level_page = 0, @notify_level_netsend =
0, @notify_level_eventlog = 2, @delete_level= 0
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

-- Add the job steps
EXECUTE @ReturnCode = msdb.dbo.sp_add_jobstep @job_id = @JobID,
@step_id = 1, @step_name = N'Update ReportSettings table', @command =
N'UPDATE [dbo].[ReportingSettings] SET [TimeDTSLastRan]=getUTCDate() ',
@database_name = N'OnePoint', @server = N'', @database_user_name = N'',
@subsystem = N'TSQL', @cmdexec_success_code = 0, @flags = 0,
@retry_attempts = 0, @retry_interval = 1, @output_file_name = N'',
@on_success_step_id = 0, @on_success_action = 1, @on_fail_step_id = 0,
@on_fail_action = 2
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXECUTE @ReturnCode = msdb.dbo.sp_update_job @job_id = @JobID,
@start_step_id = 1

IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

-- Add the job schedules
EXECUTE @ReturnCode = msdb.dbo.sp_add_jobschedule @job_id = @JobID,
@name = N'MOMGroomingFoolingSchedule', @enabled = 1, @freq_type = 4,
@active_start_date = 20050118, @active_start_time = 10000,
@freq_interval = 1, @freq_subday_type = 1, @freq_subday_interval = 2,
@freq_relative_interval = 0, @freq_recurrence_factor = 0,
@active_end_date = 99991231, @active_end_time = 235959
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

-- Add the Target Servers
EXECUTE @ReturnCode = msdb.dbo.sp_add_jobserver @job_id = @JobID,
@server_name = N'(local)'
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

END
COMMIT TRANSACTION
GOTO EndSave
QuitWithRollback:
IF (@@TRANCOUNT > 0) ROLLBACK TRANSACTION
EndSave:




--
Greetz,

Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc.
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> MOM All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB