Can I filter the data on mining structure, mining model?

I perform data mining on all products and a specific product category.
Do I need to create 2 data source views, one for all products and the other one for the specific product category?
Afterward, I run the Data Mining Wizard 2 times to create 2 mining structures.
I also need to add the same mining model (e.g. Bayes, Cluster) to each of these mining structures.
Is there any simple way to do it?

Thanks.
Joe.

Yes you'd need to use two data sources. However instead of going through the wizard twice and recreating all the contained models, you could use SQL Mgmt Studio to script the mining structure and its contained models, modify the name in the generated script and then run t. To do this, right-click on the mining structure in SQL Mgmt Studio and select "Script Mining Structure As"-> CREATE TO.

|||Thanks Raman.

Can I change row filter without disable the whole republication?

hi guys
Can I change the row filter without disable the whole republication in sql
2000?
You are best to create a new publication or if you are using dynamic
snapshots, a new snapshot.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Alien" <alien2000@.21cn.com> wrote in message
news:eUuR%23EZuFHA.3104@.TK2MSFTNGP10.phx.gbl...
> hi guys
> Can I change the row filter without disable the whole republication in sql
> 2000?
>
>

Can a trace slow down a server?

Hi

I was wondering. Can a trace slow down a server? If so, is it significant?

I got a trace that catch about 300-400 event /hour with the filter on that write its result in a .trc file used later to help analyse indexes.

Could this trace slow down a server?

Any sort of monitoring is going to have a performance hit. Unfortunately it is difficult to quantify. I would guess that the more events you capture the more impact it will have.
Try running performance monitor to assess the impact of your trace. Include the usual counters Processor, Memory and Hard disk counters (e.g. Memory : Available MBytes, Memory : Pages/sec, Processor : %Processor time, Process: Page Faults/sec, Hard disk : % Disk time, System : Context switches).
So stop the trace, start Performance monitor with your counters added, wait for a baseline to be established then restart your trace, then assess the impact.
You could use the "Index Tuning Wizard" or "Display Estimated Execution plan" in Query Analyser to analyse the effectiveness of your queries.