Extent of FullText Population

Is there a means to determine to what extent an existing
SQL table has been populated with the FullText indexing
service .... so to try to assess how long an
incremental population may take ?
Thanks
PhilipPhilip,
Yes, you can use one or more the system metadata, such as
FullTextCatalogProperty('<FT_Catalog_Name>', 'populatestatus') to monitor FT
Populations.
Note, you can also post FTS related questions to the newsgroup:
microsoft.public.sqlserver.fulltext
Regards,
John
"Philip" <plippard@.nc.rr.com> wrote in message
news:02b301c34f27$15108970$a301280a@.phx.gbl...
> Is there a means to determine to what extent an existing
> SQL table has been populated with the FullText indexing
> service .... so to try to assess how long an
> incremental population may take ?
> Thanks
> Philip

Extending native components

Can anyone provide any direction in extending existing SSIS components with a custom component, if it's possible at all. In some cases there are just slight bits of functionality missing that I think I could add in myself. But, I'm not much of a programmer and need a bit of help in the declaration of the component in my own custom component.

Thanks.I don't beleive this is possible. Whilst I am looking at the managed interfaces, not native code, they are all documented as sealed or not inheritable.

Extend existing report items

Hi,

I'm totally new to SSRS2005 and I was wondering if I could extend the existing report items. For instance, I'd like to add a few extra properties to the textbox report item. I tried wrting a custom Textbox control that inherits from System.Windows.Forms.Textbox. When I imported the dll in VS, the new textbox showed up in the toolbox, but it was grayed out.

Any idea what I'm missing here?

Thanks,
Phil
Best off writing your own and call the RS webservice.

http://msdn2.microsoft.com/en-us/library/aa179578(SQL.80).aspx|||But I want to inherit all existing functionality of the textbox... So why would I create my own from scratch?
|||Sorry, completely barking up the wrong end of the stick.

I was on about report parameter selection.

I'm guessing you can't do it.

Use Crystal Reports instead: from what I have read on these forums, it seems to do most things that RS can't.

The only reason people use RS is because they are too tight to shell out for a decent product (this has been the case where I've worked)

RS is "free". How much time have I wasted at what cost to the companies I have worked for trying to get it to do the simplest of things. Suddenly it's not so cheap, but then MS have figured out that bean counters are incapable of factoring in all this wasted time.

If only dev's got to make the purchasing decisions......

Extend CSV Rendering

Is there anyway to extend the existing CSV rending to change deviceinfo
settings that would be used when export is selected from the standard
ReportServer interface.
Example would be to have TXT rendering capability that used the CSV
rendering components, but changed the deviceinfo settings so that
Extension=txt, FieldDelimiter=|. I want to use the parameter selection
capability, and then allow the user to export to this TXT format instead of
CSV.
Logically I would think that you could added some DeviceInfo settings to the
config file in the Report Service directory where Render is defined. But I
am unable to find any sort of documentation.
Also the BOL talks about extending existing rendering formats, as opposed to
create custom rendering extensions. I have yet to find out how it is
possible to extend the CSV rendering extension to accomplish this. I really
want to be able to leverage the existing CSV rendering extension, to modify
a couple of settings.
I know that this can be done via URL and Hidden values in the calling web
page that shells the Report Services window. But when you click the Export
functionality and pick CSV none of the CSV deviceinfo settings are carried
forward to the Export window that is opened before prompting to Save or Open
the file.
Thanks,
MikeUnfortunately, we do not support setting the device info through report
manager.
Regarding the BOL reference to extending rather than writing your own: I
think this might just be a case of terminology confusion. You cannot extend
a particular format. You can extend the report server by adding your own
formats. I'll see about getting the wording changed.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael McCallum" <mmccallum@.honovi.net> wrote in message
news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
> Is there anyway to extend the existing CSV rending to change deviceinfo
> settings that would be used when export is selected from the standard
> ReportServer interface.
> Example would be to have TXT rendering capability that used the CSV
> rendering components, but changed the deviceinfo settings so that
> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
> capability, and then allow the user to export to this TXT format instead
> of CSV.
> Logically I would think that you could added some DeviceInfo settings to
> the config file in the Report Service directory where Render is defined.
> But I am unable to find any sort of documentation.
> Also the BOL talks about extending existing rendering formats, as opposed
> to create custom rendering extensions. I have yet to find out how it is
> possible to extend the CSV rendering extension to accomplish this. I
> really want to be able to leverage the existing CSV rendering extension,
> to modify a couple of settings.
> I know that this can be done via URL and Hidden values in the calling web
> page that shells the Report Services window. But when you click the
> Export functionality and pick CSV none of the CSV deviceinfo settings are
> carried forward to the Export window that is opened before prompting to
> Save or Open the file.
> Thanks,
> Mike
>|||Thanks for the information. Maybe this could be a wishlist type item?
Mike
"Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
> Unfortunately, we do not support setting the device info through report
> manager.
> Regarding the BOL reference to extending rather than writing your own: I
> think this might just be a case of terminology confusion. You cannot
> extend a particular format. You can extend the report server by adding
> your own formats. I'll see about getting the wording changed.
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
>> Is there anyway to extend the existing CSV rending to change deviceinfo
>> settings that would be used when export is selected from the standard
>> ReportServer interface.
>> Example would be to have TXT rendering capability that used the CSV
>> rendering components, but changed the deviceinfo settings so that
>> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
>> capability, and then allow the user to export to this TXT format instead
>> of CSV.
>> Logically I would think that you could added some DeviceInfo settings to
>> the config file in the Report Service directory where Render is defined.
>> But I am unable to find any sort of documentation.
>> Also the BOL talks about extending existing rendering formats, as opposed
>> to create custom rendering extensions. I have yet to find out how it is
>> possible to extend the CSV rendering extension to accomplish this. I
>> really want to be able to leverage the existing CSV rendering extension,
>> to modify a couple of settings.
>> I know that this can be done via URL and Hidden values in the calling web
>> page that shells the Report Services window. But when you click the
>> Export functionality and pick CSV none of the CSV deviceinfo settings are
>> carried forward to the Export window that is opened before prompting to
>> Save or Open the file.
>> Thanks,
>> Mike
>|||Yes, we plan (at some point :-)) to expose UI around device info settings.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael McCallum" <mmccallum@.honovi.com> wrote in message
news:%23oBG%234OGFHA.1836@.tk2msftngp13.phx.gbl...
> Thanks for the information. Maybe this could be a wishlist type item?
> Mike
> "Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
> news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
>> Unfortunately, we do not support setting the device info through report
>> manager.
>> Regarding the BOL reference to extending rather than writing your own: I
>> think this might just be a case of terminology confusion. You cannot
>> extend a particular format. You can extend the report server by adding
>> your own formats. I'll see about getting the wording changed.
>> -Lukasz
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
>> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
>> Is there anyway to extend the existing CSV rending to change deviceinfo
>> settings that would be used when export is selected from the standard
>> ReportServer interface.
>> Example would be to have TXT rendering capability that used the CSV
>> rendering components, but changed the deviceinfo settings so that
>> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
>> capability, and then allow the user to export to this TXT format instead
>> of CSV.
>> Logically I would think that you could added some DeviceInfo settings to
>> the config file in the Report Service directory where Render is defined.
>> But I am unable to find any sort of documentation.
>> Also the BOL talks about extending existing rendering formats, as
>> opposed to create custom rendering extensions. I have yet to find out
>> how it is possible to extend the CSV rendering extension to accomplish
>> this. I really want to be able to leverage the existing CSV rendering
>> extension, to modify a couple of settings.
>> I know that this can be done via URL and Hidden values in the calling
>> web page that shells the Report Services window. But when you click the
>> Export functionality and pick CSV none of the CSV deviceinfo settings
>> are carried forward to the Export window that is opened before prompting
>> to Save or Open the file.
>> Thanks,
>> Mike
>>
>|||Lukasz, Is there any complexity in rendering dynamically generated matrix
total columns in CSV format? I have been having this problem that when I
export my reports to CSV, if a matrix in the report has column groupings as
well as dynamic total columns, these total columns don't generate in CSV
version. I was thinking of writing my own CSV renderer but then I thought
there's probably a complexity into that, otherwise the Microsoft CSV renderer
would do it. Is that right? Or do you think CSV rendere just wasn't intended
to render dynamic columns in a matrix?
"Lukasz Pawlowski [MSFT]" wrote:
> Yes, we plan (at some point :-)) to expose UI around device info settings.
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Michael McCallum" <mmccallum@.honovi.com> wrote in message
> news:%23oBG%234OGFHA.1836@.tk2msftngp13.phx.gbl...
> > Thanks for the information. Maybe this could be a wishlist type item?
> > Mike
> >
> > "Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
> > news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
> >> Unfortunately, we do not support setting the device info through report
> >> manager.
> >>
> >> Regarding the BOL reference to extending rather than writing your own: I
> >> think this might just be a case of terminology confusion. You cannot
> >> extend a particular format. You can extend the report server by adding
> >> your own formats. I'll see about getting the wording changed.
> >>
> >> -Lukasz
> >>
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >>
> >> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
> >> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
> >> Is there anyway to extend the existing CSV rending to change deviceinfo
> >> settings that would be used when export is selected from the standard
> >> ReportServer interface.
> >>
> >> Example would be to have TXT rendering capability that used the CSV
> >> rendering components, but changed the deviceinfo settings so that
> >> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
> >> capability, and then allow the user to export to this TXT format instead
> >> of CSV.
> >>
> >> Logically I would think that you could added some DeviceInfo settings to
> >> the config file in the Report Service directory where Render is defined.
> >> But I am unable to find any sort of documentation.
> >>
> >> Also the BOL talks about extending existing rendering formats, as
> >> opposed to create custom rendering extensions. I have yet to find out
> >> how it is possible to extend the CSV rendering extension to accomplish
> >> this. I really want to be able to leverage the existing CSV rendering
> >> extension, to modify a couple of settings.
> >>
> >> I know that this can be done via URL and Hidden values in the calling
> >> web page that shells the Report Services window. But when you click the
> >> Export functionality and pick CSV none of the CSV deviceinfo settings
> >> are carried forward to the Export window that is opened before prompting
> >> to Save or Open the file.
> >>
> >> Thanks,
> >> Mike
> >>
> >>
> >>
> >
> >
>
>