Showing posts with label processing. Show all posts
Showing posts with label processing. Show all posts

Sunday, February 19, 2012

changing indexes

Hi, My application goes through a lengthy data processing phase before
it's ready to run. During the DP phase I'm mostly inserting records,
afterwards many of my tables will be read only. Is there anything
wrong with dropping indexes used for the DP and setting up clustered
indexes afterwards? Can I just declare my clustered indexes and go,
or do I have run some kind of statistics ...?Hi

There is nothing wrong in doing this, but it sounds like you are possibly
trying to reinvent what analysis services does!!!

If you are inserting a significant number of records your indexes may be
fragmented and therefore defragmenting them or re-creating them are
necessary activities. You may wish to change the fillfactor if your tables
are read only and have a lower fill factor whilst loading and 100% fill
factor when readonly.

You may also want to consider moving this data load offline into a separate
database, then you swap in the new data when it has been built and reduce
downtime. The whole database could be read only!

John

"Johnny Ruin" <schafer.dave@.gmail.com> wrote in message
news:1128630847.225685.79080@.g43g2000cwa.googlegro ups.com...
> Hi, My application goes through a lengthy data processing phase before
> it's ready to run. During the DP phase I'm mostly inserting records,
> afterwards many of my tables will be read only. Is there anything
> wrong with dropping indexes used for the DP and setting up clustered
> indexes afterwards? Can I just declare my clustered indexes and go,
> or do I have run some kind of statistics ...?

Thursday, February 16, 2012

Changing field type

I'm using my own data processing extension to provide a dataset to a report -
the dataset is beging generatied by VB code and passed in form of XML to the
report as a parameter. Everything works fine except from that type of all
fields is String (although they are passed as doubles in the code), so I'm
not able to show graphs on the report. I've tried to solve the problem by
adding following line:
<rd:TypeName>System.Double</rd:TypeName>
to each datafield in the RDL-file. But it didn't help.
Is it something else I could try to solve this problem?Right-click on the fields list and click "add...". Give it a name and
specify a calculated field of:
=cint(Fields!fieldname.Value)
Mike G.
"Anna" <Anna@.discussions.microsoft.com> wrote in message
news:75B8EF07-1159-4824-93F2-FDF74863DF20@.microsoft.com...
> I'm using my own data processing extension to provide a dataset to a
> report -
> the dataset is beging generatied by VB code and passed in form of XML to
> the
> report as a parameter. Everything works fine except from that type of all
> fields is String (although they are passed as doubles in the code), so I'm
> not able to show graphs on the report. I've tried to solve the problem by
> adding following line:
> <rd:TypeName>System.Double</rd:TypeName>
> to each datafield in the RDL-file. But it didn't help.
> Is it something else I could try to solve this problem?|||Anna,
Maybe it would work if you create a fuction in the Custom Code section,
which casts the strings to double's
Something like
Function ConvertToDouble(sValue as String)
return Double.Parse(sValue)
end Function
And as your chart data value you sould add
'=Code.ConvertToDouble(Fields!stringValue)' to use the convert values as your
chart input.
Jan Pieter Posthuma
"Anna" wrote:
> I'm using my own data processing extension to provide a dataset to a report -
> the dataset is beging generatied by VB code and passed in form of XML to the
> report as a parameter. Everything works fine except from that type of all
> fields is String (although they are passed as doubles in the code), so I'm
> not able to show graphs on the report. I've tried to solve the problem by
> adding following line:
> <rd:TypeName>System.Double</rd:TypeName>
> to each datafield in the RDL-file. But it didn't help.
> Is it something else I could try to solve this problem?|||Sorry, didn't notice the "double" until I read Jan's post. Of course, that
means using cdbl instead of cint. (or using Jan's suggestion and creating a
function)
Mike G.
"Mike G." <theNOSPAMjunkbox@.comcast.net> wrote in message
news:e6Mh5j0TFHA.584@.TK2MSFTNGP15.phx.gbl...
> Right-click on the fields list and click "add...". Give it a name and
> specify a calculated field of:
> =cint(Fields!fieldname.Value)
> Mike G.
>
> "Anna" <Anna@.discussions.microsoft.com> wrote in message
> news:75B8EF07-1159-4824-93F2-FDF74863DF20@.microsoft.com...
>> I'm using my own data processing extension to provide a dataset to a
>> report -
>> the dataset is beging generatied by VB code and passed in form of XML to
>> the
>> report as a parameter. Everything works fine except from that type of all
>> fields is String (although they are passed as doubles in the code), so
>> I'm
>> not able to show graphs on the report. I've tried to solve the problem by
>> adding following line:
>> <rd:TypeName>System.Double</rd:TypeName>
>> to each datafield in the RDL-file. But it didn't help.
>> Is it something else I could try to solve this problem?
>