Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

Multiple Profile Records
Last Post 01/06/2010 9:54 PM by Peter Donker. 3 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
vigorniensis
New Member
New Member
Posts:1


--
01/29/2009 12:41 AM

[I did send this to the forum yesterday but it doesn't appear and I can't help feeling this is a common experience although some people might not have realised what's happening]

It appears that DCX 5 has a very bad habit of filling up the DNN table 'Profile' with millions of records when it starts up. I noticed this because the system became sluggish and my customers were ringing up and complaining about the response and time outs.

As a temporary fix to stop this deluge happening I disabled all of the Schedule Tasks that DCX invokes and then took a couple of hours to delete the Profile records it had written away which had reached 18 million records!

This is a very bad issue and I also noticed that there were some 146,000 records sent to the Notifications file as well. This point really needs to be rectified because I certainly don't require all my users to be getting emails sent to them whenever I effect an action on DCX. I suggest that some further Settings are required urgently.

[I would be grateful, and presumably so would a few other users, if you published this issue]

 

 

 

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
01/29/2009 9:51 PM
Hi Nick,
A fix is in the making. Here is the first thing to do. This comes out of the 05.00.02 upgrade to be released soon:

IF EXISTS (select * from dbo.sysobjects where id = object_id(N'{databaseOwner}{objectQualifier}DMX_GetUsersToNotify') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE {databaseOwner}{objectQualifier}DMX_GetUsersToNotify
GO

CREATE PROCEDURE {databaseOwner}{objectQualifier}DMX_GetUsersToNotify
@PortalId int
AS

SELECT
u.*
FROM
{databaseOwner}{objectQualifier}Users u
WHERE
(SELECT COUNT(*) FROM {databaseOwner}{objectQualifier}DMX_Notifications n WHERE n.[UserId] = u.UserId AND n.[PortalId] = @PortalId AND n.[Sent] IS NULL)>0

GO

Run the above in Host > SQL and the amount of transactions on the notification should deminish greatly (if you have a massive amount of users that is).

Peter
Ben
New Member
New Member
Posts:1


--
01/05/2010 7:30 AM

Peter this issue still persists. 

Since turning the scheduler back on DMX has created over 4 Million notification records.

DMX is only used by 100 users in 1 Portal.  However I can find Notification records for UserId's that belong the other 340 Portals and 500,000 Users who have no links to the Portal DMX is installed in. 

Could you please assist ASAP.

Thanks

Ben

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
01/06/2010 9:54 PM
Hi Ben,

Notification records are not the same as profile records. I believe the profiles are no longer touched. The notifications you see are probably a result from a first sweep which takes all overdue notifications. You can go to SQL and set the SENT column to GETDATE() (i.e. now) for all records to fool the system into thinking that all notifications have been sent. From then on all notifications should run normally with a normal amount of records being created.

Peter
You are not authorized to post a reply.