Showing posts with label basic. Show all posts
Showing posts with label basic. Show all posts

Sunday, March 25, 2012

Cluster Names

I have a basic segmentation model that uses the clustering algorithm. I've renamed the clusters in the cluster diagram, but they still show up as Cluster 1-n in the dimension browser and in the cube browser.

After renaming the clusters, I did a full reprosses on the data mining dimension and on the linked cube. Can anyone tell me what else I need to do to use the new cluster names in the report?

Thanks

A full reprocess of the DM dimension and the linked cube should do the trick - in fact, you don't really need to reprocess the cube with the linked DM dimension. Are you sure the reprocess completed successfully and you refreshed the dimension/cube browsers?|||

Yes. I tried it again with the same results. I noticed that when I opened the project that the cluster names that I entered were gone. The model had Cluster 1-10 again. I renamed them again, saved the .dmm file, reprocessed the dimension (full, successful), and reconnected in the browser. It still shows Cluster 1-10. I tried re-processing the model. That resets the cluster names in the model viewer.

Thanks for your help Raman.

|||

Renaming clusters in the viewer directly updated the model on the server - there is no need to reprocess the model. What you're seeing still looks like a client refresh issue.

What version of the Analysis Services 2005 and client tools (BI Dev Studio) are you running? RTM or SP1? Would you be able to provide complete repro steps for this problem?

|||

SP1, using BIDS to browse

In trying to re-create the problem in AdventureWorks, I found that changing the cluster names worked. I noticed the AllowDrillthrough setting in the AW cluster model was set to True. After changing that property in my project, the cluster names showed in the dimension. This seems to fix the problem.

Thanks for your help Raman.

sqlsql

Monday, March 19, 2012

Cluster / SQL 2005 / SAN storage

Hi...I got some basic questions in regards to setup a lab environment
with two nodes cluster over Windows ent 2003, ent SQL 2005 and SAN
storage.
1) Would the following hardware be enough: SAN storage, fiber channel
switch, two intel servers, 4 HBA (2 for each servers) ?
2) what is the difference betwen fiber channel switch and fiber
channel routing?
3) what is different between fiber channel and iSCSI?
4) what is the zoning?
5) what is the steps to install the cluster windows server?
6) what is the steps to configure the SQL2005? do I need to install
SQL twice in each node, or I just need to install once in the vitual
server?
7) what is the draft diagram?
8) what is the private network, public network for SAN?
Thanks,
Yve

> 1) Would the following hardware be enough: SAN storage, fiber channel
> switch, two intel servers, 4 HBA (2 for each servers) ?
Best practice would be to have two FC switches to create two fabrics for
redundancy. Also as you mention 2 HBA's per node, you probably want "Multi
path software", contact your storage vendor to get more information.

> 2) what is the difference betwen fiber channel switch and fiber
> channel routing?
Switching is done within a fabric. In VERY large installations, routing
might be needed to "route" between various fabrics, most installations, even
with multiple fabrics, you would find switches only. If you only build a
cluster in a lab, you would not need routing.

> 3) what is different between fiber channel and iSCSI?
iSCSI runs over IP protocol, iSCSI is deemed to be more cost efficient,
however when building a SAN there are many questions on cost, speed,
performance, interoperability and reliability (.. .and so on).

> 4) what is the zoning?
In a Fibre Channel Fabric, Zoning determines which HBA can talk to which
port on the Storage.
(e.g. HBA-1 from Server-2 can communicate to Port-X on Storage-A) this
allows multiple Servers and multiple Storage units to be connected to a
Fabric, without "conflicting" traffic on your SAN)

> 5) what is the steps to install the cluster windows server?
Have a read of this first:
- http://technet2.microsoft.com/windowsserver/en/technologies/genclust.mspx
A good collection of cluster related articles can be found here:
- http://www.nw-america.com/

> 6) what is the steps to configure the SQL2005? do I need to install
> SQL twice in each node, or I just need to install once in the vitual
> server?
Have a read about this in the online books

> 7) what is the draft diagram?
I leave this to SQL guys to answer

> 8) what is the private network, public network for SAN?
- private network is the IP network between the Cluster Nodes for cluster
(only) communications
- public network is the IP network both nodes are connected to, and which
will be used for users to connect to your clustered SQL databases
- private/public networks have nothing to do with SAN, SAN is the network
(FC or iSCSI) which connects your nodes to the shared storage.

> Thanks,
> Yve
>
Hope this helps,
Rgds,
Edwin.

Sunday, March 11, 2012

CLR Question (BASIC)

I have Visual Studio .Net 2003...I am assuming that since it can't find
System.Data.SQLServer that I need Visual Studio 2005 to develop CLR apps for
SQL?Hello RSH,

> I have Visual Studio .Net 2003...I am assuming that since it can't
> find System.Data.SQLServer that I need Visual Studio 2005 to develop
> CLR apps for SQL?
Correct
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||There's no System.Data.SQLServer anymore. You use the regular connection obj
ects, reader etc. For
SQLCLR specific things (like context and pipe), you use the Microsoft.SqlSer
ver.Server namespace.
You do need Framework 2.0 (as the things you need are in the System.Data.dll
file that comes with
Framework 2.0). You can download Framework 2.0 and write your CLR objects us
ing Notepad and
command-line compile them. If you want to use VS to write SQLCLR objects you
need VS 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"RSH" <way_beyond_oops@.yahoo.com> wrote in message news:ejDCfJ29FHA.160@.TK2MSFTNGP12.phx.gb
l...
>I have Visual Studio .Net 2003...I am assuming that since it can't find Sys
tem.Data.SQLServer that
>I need Visual Studio 2005 to develop CLR apps for SQL?
>|||You don't really need Visual Studio at all. You can download the .NET 2.0
SDK and use the command-line tools. But if you want the IDE experience,
yes, VS2005 is necessary.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"RSH" <way_beyond_oops@.yahoo.com> wrote in message
news:ejDCfJ29FHA.160@.TK2MSFTNGP12.phx.gbl...
>I have Visual Studio .Net 2003...I am assuming that since it can't find
>System.Data.SQLServer that I need Visual Studio 2005 to develop CLR apps
>for SQL?
>

Sunday, February 19, 2012

Client Side Redirect - Database Mirroring

Hi All,

My apologies if this question seems abit basic, but I'm a DBA by trade and programming .Net isn't my strong point ;)

I've enabled database mirroring on 3 SQL 2005 servers, a principal, a mirror and a witness.

Principal - SQL 2005 Enterprise Edition, SP1

Mirror - SQL 2005 Enterprise Edition, SP1

Witness - SQL 2005 Express, SP1

I've written some test code to test the mirroring but as soon as the connection is pulled from the principal, the client re-direct doesn't work and the program bombs. I'd be grateful fi someone could have a look at my code below and tell me if there's any schoolboy errors?

(NB, the user running the code is a sys admin on all 3 servers)

Thanks in advance.

Imports System.Data.SqlClient

Public Class Form1

Dim DCTADS As New SqlClient.SqlConnection

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

DCTADS.ConnectionString = "Network=dbmssocn; Server=STUD; Failover Partner=DBDRTEST; Database=mirrortest; Integrated Security=True"

DCTADS.Open()

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click

Dim cmd As New SqlClient.SqlCommand

cmd.CommandText = "Select fulldesc from unclproduct where internal = '20000110'"

cmd.Connection = DCTADS

Dim dr As SqlClient.SqlDataReader

dr = cmd.ExecuteReader

MsgBox(DCTADS.DataSource.ToString)

If dr.Read Then

MsgBox(dr("fulldesc").ToString)

End If

dr.Close()

End Sub

End Class

Here is more detailed discussion for client redirect (http://msdn2.microsoft.com/en-us/library/ms366348.aspx). From the code I did not see any problem. One thing to check is to make sure the TCP/IP and "allow remote connection" are enabled on both principal and mirror because by default these two settings are disable after SQL server is installed.