Latest posts for the topic "How large is your helpdesk database"

How large is your helpdesk database

JSH — GMT

We are using MS SQL 2005 and currently the size is almost 4 GB. (Been using Sysaid for 9 month now and have 3500 ServiceRequests)

Anyone else that would like to comment. I don't know if this is normal

How large is your helpdesk database

Haim — GMT

Hey JSH.

Please check what is the size of the SysAid database LDF file.
If it is bigger then a few hundred MB, you can shrink it by backing up your database.

4GB is a pretty large size but can be reasonable if you are using SysAid to audit a large number of assets or if you attached a lot of files into SysAid.

Best regards.
Haim

Re:How large is your helpdesk database

JSH — GMT

The LDF-file is only 3-4 MB

Just did a shrink on it. (shrinking the database on a weekly basis)

Re:How large is your helpdesk database

EbroIN — GMT

Hi JSH,

same found [url=http://www.ilient.com/Sysforums/posts/list/2098.page#9964]here[/url]

I've posted almost the same question a few weeks ago.

I think it is all about windows updates. Everytime a client gets a windows update the table 'computer_history' grows No secret that every 2 weeks there are a few updates available which leads to that issue, that the size of the table 'computer' gets added to the table 'computer_history'... and on my installation this is growing the database...

So I've started a [url=http://www.ilient.com/Sysforums/posts/list/2176.page#10304]Feature Request[/url] to avoid those updates being logged, hoping that it'll keep my database lean.

Can you find out WHAT database table is growing that fast?
I found a real nice stored procedure* around the internet and will attach it here for your convenience

Best regards,

EbroIN

[edit]
* = This is only the executed part of the stored procedure! You must generate a stored procedure for your database to integrate this script! Thanks to JSH he informed me about my ambiguous post here. So create a new stored procedure and post the SQL statemenents here. I've left all comments from the author inside this script (as told, I've found this script in the internet).

Re:How large is your helpdesk database

JSH — GMT

When running the SQL as a new query I get the error :

Msg 102, Level 15, State 1, Line 46
Incorrect syntax near 'END'.

Re:How large is your helpdesk database

EbroIN — GMT

[quote=JSH]When running the SQL as a new query I get the error :
Msg 102, Level 15, State 1, Line 46
Incorrect syntax near 'END'.[/quote]

Oops, copied too much. You have to include this query into a stored procedure or this won't work.
I've removed the END command so this won't bother you anymore -> Thanks.

I cannot provide a complete SQL Solution for you, so you need to use SQL Studio Express (or something like this) in order to wrap this script inside such a wrapper (assuming your database is named ilient as default):

[code]
USE [ilient]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE PROCEDURE [dbo].[helpers_tableInfo]
AS
BEGIN
SET NOCOUNT ON

/* NOW PASTE THE ABOVE SCRIPT IN HERE! */

END
[/code]

This will create a stored procedure....

You then need to execute the stored procedure with the following SQL commands (still assuming that your database is named ilient and the freshly created stored procedure is named helpers_tableInfo)

[code]
USE ilient
GO
EXECUTE helpers_tableInfo
GO
[/code]

Alternatively you can simply create a new stored procedure using the SQL Server Management Studio.

SQL Server Management Studio --> Ilient --> Programmability --> Stored Procedures <-- RIGHT CLICK
Select --> New stored procedure

Paste the above code (including the pasted script - use the text editor of your choice) inside the Query Window (clear all existing code before) and hit APPLY only ONCE. This will create the procedure.

Afterwards you need to refresh the view (hit F5) and right click on your new stored procedure (it should show up by now).
Select --> Execute stored procedure --> Confirm with OK

This should do the trick...

I'll just modify my previous post and cut the last line (containing the END command)

Hope this helps,

best regards, EbroIN

Re:How large is your helpdesk database

JSH — GMT

Just got another version of the SQL-statement and now I have the stored procedure - result:

Re:How large is your helpdesk database

Mucho — GMT

We have 10k service request and our sql server database in simple recovery mode have 3330 MB

Re:How large is your helpdesk database

EbroIN — GMT

Hi,

back from my short holiday,

my database hasn't grown too much, waiting for the update cycle today ...

best regards,

EbroIN

Re:How large is your helpdesk database

DK_Sysaider — GMT

We have nearly 600 service requests, and a database on 1 GB, still in the built in Derby database.

Re:How large is your helpdesk database

EbroIN — GMT

[quote=DK_Sysaider]We have nearly 600 service requests, and a database on 1 GB, still in the built in Derby database.[/quote]

Hi DK_Sysaider,

how many assets are you monitoring using sysaid?
I suppose that computer_history is the "largest" table within my complete configuration...

Greetings - EbroIN

How large is your helpdesk database

Haim — GMT

Hello everyone.

We have found that the "computer history" can grow too much in size on some cases.
We have identified the issue and we are working on a minor patch that will resolve this issue.

Meanwhile, if the computer history grow too much you can truncate it to keep the database size down until the fix will be available.

We are very sorry for the inconvenience

Best regards.
Haim

How large is your helpdesk database

EbroIN — GMT

[quote=Haim]...we are working on a minor patch that will resolve this issue.[/quote]

Hi Haim,

thanks for your feedback...

Would you please inform us, when this patch is available?

Thanks

Re:How large is your helpdesk database

DK_Sysaider — GMT

[quote=EbroIN][quote=DK_Sysaider]We have nearly 600 service requests, and a database on 1 GB, still in the built in Derby database.[/quote]

Hi DK_Sysaider,

how many assets are you monitoring using sysaid?
I suppose that computer_history is the "largest" table within my complete configuration...

Greetings - EbroIN[/quote]

Sorry for the late responds, we are monitoring about 70 Assets..
I think it's is, we have one problem in the Activity log, this is shown all over:

[list]Software Product Windows Genuine Advantage Validation Tool (KB892130) version changed from null to 1.7.0069.2 [/list]
Being "updated" at every inventory check, at the most assets. It gives quite an log I guess .
I saw something earlier on the forum that there was a fix for this underway, and it could be in the version 6, but its still an issue.
But we can live with it.

How large is your helpdesk database

Haim — GMT

DK_Sysaider,

Please check if you are using version 6 of the agent on the machines who are having this issue as this issue should have been resolved in version 6 of the agent.

EbroIN,
We have postponed the official release of patch 6.0.07 to include this fix in the final edition, I hope we will have the patch ready by the end of the week.

Best regards.
Haim

Re:How large is your helpdesk database

techguy — GMT

[quote=Haim]
We have postponed the official release of patch 6.0.07 to include this fix in the final edition, I hope we will have the patch ready by the end of the week.[/quote]

is it going to have a different version number then when it is finally released? as some of us are already on 6.07, and that is going to get confusing if there are 2 versions with the same number.

How large is your helpdesk database

DK_Sysaider — GMT

[quote=Haim]DK_Sysaider,

Please check if you are using version 6 of the agent on the machines who are having this issue as this issue should have been resolved in version 6 of the agent.
[/quote]

I thought so I read this should been fixed in v6, but I do still have this problem. But I'll try and check the computers still reporting it, how do you check the version of the agent on a computer?

How large is your helpdesk database

Haim — GMT

[quote=DK_Sysaider][quote=Haim]DK_Sysaider,

Please check if you are using version 6 of the agent on the machines who are having this issue as this issue should have been resolved in version 6 of the agent.
[/quote]

I thought so I read this should been fixed in v6, but I do still have this problem. But I'll try and check the computers still reporting it, how do you check the version of the agent on a computer?[/quote]

The best way to see the agent version is to add the "SysAid agent version" column to the asset list using the "customize list" button.

Let me know on what you find

Haim

Re:How large is your helpdesk database

techguy — GMT

Did you miss my question above?

How large is your helpdesk database

DK_Sysaider — GMT

[quote=Haim]
The best way to see the agent version is to add the "SysAid agent version" column to the asset list using the "customize list" button.

Let me know on what you find

Haim[/quote]

Okay thank you Haim.
I was sure I had a regular agent update scheduled long time ago when I moved SysAid, but must have forgotten to save. I also forgot to update the package for our group policy, so new computers get the old version. I ran a update and scheduled one every week, and the agents are updating just fine now, and I think the problem with changing version from null stopped at least it looks like. I'll monitor it the following days, but think its okay now.

Re:How large is your helpdesk database

Haim — GMT

[quote=techguy]Did you miss my question above?[/quote]

Hey Techguy.

The next patch that will be released will not be called 6.0.07, i'm not sure what will be the official name, and i will let you know in the next few days when it will be released.

Best regards.
Haim

Re:How large is your helpdesk database

JSH — GMT

well, two month later, running on Sysaid Server 6.0.0.7 and clientAgent 6.0.0.7

Our database is now 8.2 GB, which I think i alarming. Shrinking the DB will only give us 5 MB.

What to do?? is there no other way than a complete reinstall on a new DB??

How large is your helpdesk database

Haim — GMT

JSH,

Please upgrade to version 6.0.09.
Also, if you are using MS-SQL, please check the size of the log file (LDF file), and if it take a big size, you can shrink it by backing up your database.

Best regards.
Haim