|
| | | Junior Member
 
Group: Forum Members
Last Login: 7/14/2008 2:11:22 PM
Posts: 16, Visits: 40 |
| | Robert: Glad to hear that WUG is working for you! I was able to reproduce the problem after clicking the "Optimize the selected tables..." button. Thanks for your report! I have create a defect for this issue. I also tried to shrink the database used "dbcc shrinkdatabase ('whatsup', 0)" command and get the database size down significantly. For me, the "dbcc shrinkdatabase('whatsup', TRUNCATEONLY) doesn't work - the database size remains the same. I created another defect for our "Validate and Compact database" button doesn't shrinkdatabase size. Thanks for help us identify the problems!!! Min |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 9/5/2008 6:16:45 PM
Posts: 2, Visits: 19 |
| Min,
I am running Server 2003 R2 Service Pack2 with all updates. First I did a fresh install of Version 12 then restored the database and ran the database upgrade scripts. The service would never start then it would always crash. The original database was the MSDE on version 11.03. The service would crash with:
Faulting application NMService.exe, version 12.0.1.877, faulting module msvcr80.dll, version 8.0.50727.1433, fault address 0x000127da.
I then tried installing version 11.03 and importing the database making sure it was running ok. Then tried the upgrade to version 12 and applying the patch but the service would crash with the same error:
Faulting application NMService.exe, version 12.0.1.877, faulting module msvcr80.dll, version 8.0.50727.1433, fault address 0x000127da.
So for now I have stuck with version 11.03 but did move the database to an external SQL 2005 SP2 and the WUG 11.03 is running on Server 2003 R2 Service Pack 2 with all updates. I figure I would leave it like that until the issues with version 12 are resolved before trying to run the latest version again.
Thanks and let me know if you need more info.
Craig
|
| |
| | | Junior Member
Group: Forum Members
Last Login: 7/14/2008 2:11:22 PM
Posts: 16, Visits: 40 |
| | Craig: Are you running WUG and database on the same server? The V12.0.2 patch fixed the problems with WinEventLog passive monitors with wrong window's credentials. Before you run the upgrade, could you please check if all your WinEventLog Passive monitors has correct window's credentials assign to the devices? If you can send me your V11.0.3 database (Console -> Tools -> Database Utilities -> Backup database...), I will try to reproduce your problem on my window's 2003 server - this will help us a lot if we see the problem. My email is: mzhang@alpha.ipswitch.com. Min |
| |
| | | Junior Member
Group: Forum Members
Last Login: 7/11/2008 10:40:01 AM
Posts: 11, Visits: 17 |
| Min -
Glad to hear it could be duplicated, i thought i was insane there for a minute!
For anyone using the full version of SQL2005 I highly recommend using "SQL server management studio", or "Microsoft SQL Server Management Studio Express" for people using the standard 5g version that comes with WhatsUp. It will give you a little greater control and allow you to recover faster. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 7/14/2008 11:18:20 AM
Posts: 3, Visits: 18 |
| @MIN
Sorry, but currently the database has a size of 30GB.
It seems that after the patch, the database has doubled its size as reported from other users. And now it seems to grow more that expected. Before we installed the patch, our database had a size about 8GB.
It seems that something was wrong with the patch.
I´m not very familiar with MS SQL like Robert so what can we do now now ?
|
| |
| | | Junior Member
Group: Forum Members
Last Login: 7/11/2008 10:40:01 AM
Posts: 11, Visits: 17 |
| | AJ - If you installed the full version of SQL you should have "SQL Server Management Studio". I think it gets installed by default when you install sql2005. |
| |
| | | Junior Member
Group: Forum Members
Last Login: 7/14/2008 2:11:22 PM
Posts: 16, Visits: 40 |
| | AJ: Can you run this sql cmd to find out which tables take most of the space? You can also run it to find out how fast the tables grow. Let us know the result. As Robert points out, you can use "SQL Management studio" to run the queries. If not, you can use these cmd from "cmd" prompt. ================= Shrink database manually ====================== * backup your database (You can use WUG utility to backup); * Or run the sql cmd from cmd prompt - to shrink database manually: C:\Windows\system32>sqlcmd -S (local)\WhatsUp -d whatsup -Q "dbcc shrinkdatabase ('WhatsUp'
, 0)" ================= Find out the table sizes/space used ============== See the attached file: Space_Used.txt for the sql command. If you have SQL Management studio, open the file in SQL Management studio and execute it. Otherwise, you can run this command: C:\Windows\system32>sqlcmd -S (local)\WhatsUp -d whatsup -i "[path]\Space_Used.txt" -o "[path]\yourResult.txt" [path] is where you put your "Space_Used.txt" file. For example, c:\dbScripts\. Min
|
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 7/14/2008 11:18:20 AM
Posts: 3, Visits: 18 |
| Friday evening I did the following actions:
- Table Maintenance - Purged expired rows
- Check for fragmented tables and optimize selected tables
- Validate and compact database
While running these actions the database grew up to 36GB. After the "validate and compact..", the database were shrinked down to 7GB.
But the error message
"CHECKCONSTRAINTS:
Error in table '[dbo].[PivorReportToCategory]': value '[nWebUserID = '2'' violates '[FK_PivutReportToCategory_nWebUserID]'."
still occurs running the "validate and com...".
I will have a look at the database size the next days and will run further investigations with your script suggestions when the database starts to grow abnormal.
But I still want to know what this checkconstraints-error means ?
|
| |
| | | | |
|