Wednesday, March 7, 2012
deploying CLR objects best practice
When I want to deploy CLR assemblies on a SL Server Production Server. What
is the best pratice to define where to store theses assemblies?
In the case of deploying with VS 2005, where the tool put the assemblies on
the server?
Thanks in adavance,
LaurentAssemblies are stored in databases, no matter if you deploy them using
CREATE ASSEMBLY command of VS.NET IDE deployment. Therefore, store the
assembly in the database where you need your CLR objects.
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com
"laurent banon" <laurent.banon@.soorce.com> wrote in message
news:uNPGDOl%23FHA.2812@.TK2MSFTNGP09.phx.gbl...
> Hi,
> When I want to deploy CLR assemblies on a SL Server Production Server.
> What is the best pratice to define where to store theses assemblies?
> In the case of deploying with VS 2005, where the tool put the assemblies
> on the server?
> Thanks in adavance,
> Laurent
>
Friday, February 17, 2012
Dependency network question!!
The thing is: when i create a new AS project in my visual studio define data source view and create model, let it be decition tree, i can see "dependency network" where i can figure how one column relate to another.
I want to use this knowledge in my C# application in order to choose right column to my next task. How do i get the result using dmx or amo? Do you have any idea?
Run SQL Server Profiler when opening dependancy network tab of the viewer. You will see what store procedure the viewer calls to display the dependency network. Then call the store procedure from your C# application.
Here is what you get back from the store procedure. (I executed
CALL System.Microsoft.AnalysisServices.System.DataMining.DecisionTreesDepNet.DTGetNodeGraph('v Target Mail', 60) )
NODE_TYPE NODE_UNIQUE_NAME_1 NODE_UNIQUE_NAME_2 MSOLAP_NODE_SCORE
1 3 Date First Purchase
1 0 Bike Buyer
1 2 Commute Distance
1 5 English Occupation
1 4 English Education
1 1 Birth Date
2 5 0 1
2 2 0 4
2 3 0 5
2 1 0 3
2 4 0 2
NODE_TYPE 1 is a node, NODE_TYPE 2 is an edge.
Node "Date First Purchase" has an ID 3, "Bike Buyer" has an ID 0, "Commute Distance" has ID 2 etc.
The strongest edge with MSOLAP_NODE_SCORE = 5 goes from node 3 to node 0, i.e. from "Date First Purchase" to "Bike Buyer".
Tatyana
|||Great thx a lot... it helps me more than you can imagine. Take care TatyanaLangsuyuar
Dependency network question!!
The thing is: when i create a new AS project in my visual studio define data source view and create model, let it be decition tree, i can see "dependency network" where i can figure how one column relate to another.
I want to use this knowledge in my C# application in order to choose right column to my next task. How do i get the result using dmx or amo? Do you have any idea?
Run SQL Server Profiler when opening dependancy network tab of the viewer. You will see what store procedure the viewer calls to display the dependency network. Then call the store procedure from your C# application.
Here is what you get back from the store procedure. (I executed
CALL System.Microsoft.AnalysisServices.System.DataMining.DecisionTreesDepNet.DTGetNodeGraph('v Target Mail', 60) )
NODE_TYPE NODE_UNIQUE_NAME_1 NODE_UNIQUE_NAME_2 MSOLAP_NODE_SCORE
1 3 Date First Purchase
1 0 Bike Buyer
1 2 Commute Distance
1 5 English Occupation
1 4 English Education
1 1 Birth Date
2 5 0 1
2 2 0 4
2 3 0 5
2 1 0 3
2 4 0 2
NODE_TYPE 1 is a node, NODE_TYPE 2 is an edge.
Node "Date First Purchase" has an ID 3, "Bike Buyer" has an ID 0, "Commute Distance" has ID 2 etc.
The strongest edge with MSOLAP_NODE_SCORE = 5 goes from node 3 to node 0, i.e. from "Date First Purchase" to "Bike Buyer".
Tatyana
|||Great thx a lot... it helps me more than you can imagine. Take care TatyanaLangsuyuar