Profiler Is Only Sampling Data

dataservices job design
1

I’ve been using the built-in DS Profiler on a project for the past few months. Last week I changed the Profiler Configuration property “Number of days to keep results” to 365 so the profiles would stick around longer.

Now the Profile is only sampling a subset of rows, somewhere around 1%. Previously it was reading all the rows. The “Profiling size” property is still set to “All”. I never changed that.

Any idea why it’s only sampling the data now?

Where are the Profiler configuration values stored? I looked in the schema for the Profiler repository and found the PF_CONFIG table, but it is completely empty. I searched the O/S where the Job Server resides but didn’t find any obvious files.

eganjp :us: (BOB member since 2007-09-12)

2

I changed the Profiling Size property to “999999999” instead of “All”. That didn’t help one bit. I may try recreating the profiler repository from scratch. However, if those settings aren’t stored in the repository I don’t see how that is going to fix the problem.

eganjp :us: (BOB member since 2007-09-12)

3

Did you tried to change back the “Number of days…etc” to it original value?

I don’t use profiler a lot, but maybe the problem if related to an undocumented relation between does parameters.

Regards,

Andrés

aidelia :argentina: (BOB member since 2006-02-02)

4

Changing the retention days back to 30 didn’t help. Good thought though. Of course, I lost all my profiles older than 30 days. LOL!

eganjp :us: (BOB member since 2007-09-12)

5

Could it be in the DS Config file? That’s the only other place I can think of aside from the repository itself.

ErikR :new_zealand: (BOB member since 2007-01-10)

6

There is a profiler section in DSConfig.txt, but I’m not seeing any properties in that section (or any other) that relate to this problem.

eganjp :us: (BOB member since 2007-09-12)

7

Did you restart the job server in between making this change? Maybe something just got porked and restarting the job server service may bring it back to normal?

ErikR :new_zealand: (BOB member since 2007-01-10)

8

I detached the profiler repository from the job server and the CMC, started over from scratch with a clean repository using Repository Manager and then hooked everything back up. A restart of the job server was performed after detaching and after reattaching the profiler repository.

The profiling is still doing a sample of rows instead of all rows. So none of the above changes made any difference at all. My “Profiling size” property is showing “All”.

eganjp :us: (BOB member since 2007-09-12)

9

So the problem doesn’t seem to be “in” the repository itself…DSConfig perhaps? Registry?

Other than a reinstall of Data Services I wouldn’t know any other way to fix it?

ErikR :new_zealand: (BOB member since 2007-01-10)

10

Registry??? Uhmmmm tell us more, c’mon.

I’ve have a lot of trouble with the Windows Registry but regarding IPS when we tried to downgrade a failed install.

But never heard of registry settings for DS Designer nor Job Server.

Regards,

Andrés

aidelia :argentina: (BOB member since 2006-02-02)

11

I haven’t checked the registry for settings. I would not expect to find them there.

Some .xml file, maybe? I know that the timeout for connections to the management console are in a .xml file. I tweaked that one a few weeks ago.

eganjp :us: (BOB member since 2007-09-12)

12

I think the problem is within the profiling job itself. The profiler configuration screen within the Management Console says to sample “All” rows. But it is clearly sampling a very small subset of rows. The number of rows sampled varies from table to table. It looks like it is sampling around 2%.

In the server_eventlog file I can see that the call to run the profiling job is using “All” as a parameter. Somehow the job is ignoring that parameter.

I can’t find an ATL file that has the source code for the profiling job. :frowning:

eganjp :us: (BOB member since 2007-09-12)