Problems Deleting / Renaming Dimensions

I had a problem with a dimension and so decided to re-created it. Once I was happy with the new dimension I deleted the old and renamed the new to what the old one was called previously. When I try and build my cube I get the following error:

Error 18 Errors in the metadata manager. The dimension with the name of 'dim_product' already exists in the 'Sales_AS' database.

Not sure why this is happening as I thought I'd got rid of all trace of the old dimension. If I rename the new dimension I have no problem.

Is anyone able to explain what's going on here? Thanks.

If you deploy with the default settings the old dimension still exists on the server and if you want too deploay a second one with the same name (but for sure a different id) the server does not allow this.

Try delete the DB from Analysis services and deploy the whole DB again (if possible for your solution).

HANNES

Problems Creating TVF function

I had succesfully created a CLR function which was fully operational on the development server. Today the powers that be decided to do a full restore from the Production server because the wanted the most recent data on the server. Since our code has not been deployed to production I went through the exercise of redeploying everything to the server and all goes well until I try to create the function:

Code Snippet

CREATE FUNCTION f_GetGroupMembership(@.providerKey nvarchar(200), @.connection nvarchar(1000))

RETURNS TABLE (groupID uniqueidentifier, groupName nvarchar(100), groupType nvarchar(25))

AS

EXTERNAL NAME NavigatorSecurity.groups.GetGroupsForUser

This returns an error:

Msg 10305, Level 16, State 1, Procedure f_GetGroupMembership, Line 1

The Init method for a CLR table-valued function must be annotated with SqlFunctionAttribute.

Now remember this CLR was working correctly previous to the restore from backup. But just in case I got a case of dumb*** I checked my clr code anyhow here it is:

Code Snippet

using System;

using System.Data;

using System.Data.Sql;

using System.Data.SqlTypes;

using System.Data.SqlClient;

using Microsoft.SqlServer.Server;

using System.DirectoryServices;

using System.Collections;

public class GroupMembership

{

[SqlFunctionAttribute(FillRowMethodName = "FillGroupRow")]

public static IEnumerable GetGroupsForUser(String ProviderKey, String Connection)

{

return groups.GetGroupsForUser(ProviderKey, Connection);

}

public static void FillGroupRow(Object obj, out SqlGuid guid, out SqlString name, out SqlString type)

{

//cast the enumerator passed in

group grp = (group)obj;

//create output parameters

guid = new SqlGuid(grp.guid);

name = new SqlString(grp.Name);

type = new SqlString(grp.applicationData);

}

}

Can anyone tell me why this is happening? How can I overcome this problem?

Help will be highly appreciated.

Help Please! there is no reference to this error anywhere|||
In your CREATE FUNCTION statement, you are referencing the wrong class, groups.GetGroupsForUser instead of GroupMembership.GetGroupsForUser.|||

Steven,

Thank you I figured out I did not reply here because I did not want to look like the dumba** that I am. Thanks Anyway. I'll try to review my code a third time before I make a fool of myself in public.

Regards,

MB

Problems connecting to MSDE from other PC

Hello,
We are a small software developement group. Recently we decided to try out
using MSDE, and one of our developers installed it on his PC. After some
struggling with logging on it was discovered that by default it uses Windows
authentication mode and reading KB articles we were able to change the auth
mode to mixed. Now he is able to connect to the local MSDE server using
login "sa" and the install-time defined password, using the freeware tool
"Toad for MSSQL server". It's interesting, that it connects successfully, if
in the "server" is given the computer name, but wouldn't connect if IP
address 127.0.0.1 or LAN address starting with 192.168.*.* is used.
However, there are problems in attempting to connect to this server from
other PCs on our LAN, that have SQL Enterprise managers installed. It just
reports that "Server does not exist or access denied". Does MSDE even
support remote connection with SQL EM? Or, should I somewhere enable it?
Perhaps I am missing something here. It would be great to be able to connect
to this MSDE from other PCs, using EM to compy data to and from databases.
Thanks,
Pavils
I discovered, that is was related to the disabled network drivers.
Reinstalling with the network support solved the problem.
Pavils
|||Pavils Jurjans wrote:
> *I discovered, that is was related to the disabled network drivers.
> Reinstalling with the network support solved the problem.
> Pavils *
I'm having similar problems. Are you saying it's a problem with the
machine's network drivers, not MSDE?
Thanks,
Russell
russmail
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message361867.html

Problems connecting to MSDE from other PC

Hello,
We are a small software developement group. Recently we decided to try out
using MSDE, and one of our developers installed it on his PC. After some
struggling with logging on it was discovered that by default it uses Windows
authentication mode and reading KB articles we were able to change the auth
mode to mixed. Now he is able to connect to the local MSDE server using
login "sa" and the install-time defined password, using the freeware tool
"Toad for MSSQL server". It's interesting, that it connects successfully, if
in the "server" is given the computer name, but wouldn't connect if IP
address 127.0.0.1 or LAN address starting with 192.168.*.* is used.
However, there are problems in attempting to connect to this server from
other PCs on our LAN, that have SQL Enterprise managers installed. It just
reports that "Server does not exist or access denied". Does MSDE even
support remote connection with SQL EM? Or, should I somewhere enable it?
Perhaps I am missing something here. It would be great to be able to connect
to this MSDE from other PCs, using EM to compy data to and from databases.
Thanks,
PavilsI discovered, that is was related to the disabled network drivers.
Reinstalling with the network support solved the problem.
Pavils

PROBLEM: Grouping tasks: Connections disappear ?

Guys,

anyone seen this before?

I've just finished me lovely big package.. decided to tidy it up and make it look nice...
(when will I ever learn?)

So I selected a few tasks, right clicked and selected "group". Named the group.....

And now all the connectors between the tasks in the group have disappeared.... tried ungrouping.. still not there...

The package still runs fine... the tasks are executed in the right sequence and all that... but the connectors are jut not visible...

If I try to recreate the connector I get an error dialog saying "Cannot create connector. Only one workflow can exist between the same two executeables.". So they must still exist...

It'd be ok to leave it as it is I suppose.. if I didn't now need to modify the precedence constraint on one of the connectors.... and I can't actually select the feckin connector..

Any suggestions? Any way to refresh the display? Have already exited the environment and come back in.. will try rebooting machine now anyway...

PJ

I've seen problems like this before. Sometimes moving the tasks about makes them reappear. If not, you might be stuck.

In my opinion its a bug.

-Jamie

|||

They're back!

Phew..

I started copying and pasting new versions of the tasks... thinking I could delete the old ones and reconnect the new ones...

And after the first copy and paste... the connections reappeared...magic!

Suppose its good to have a note about this somewhere in the forums for anyone else that comes on this problem...

Now I'm off to get this thing into Sourcesafe (which I should have done from the start)

Thanks Jamie,

PJ

problem with xsd and doulbe nested tags

I am having a problem with an xsd design (again). The client has decided to make a change and everything I try does not work. They have ADDED a nested tag to a nested tag - a person can have multiple addresses. There is a <PERSONID> tag that appears under
the <LIST> tag at the same level as the new tags. I need the ADDRESS info to end up in an ADDRESS table, with the PERSONID populated. The tags appear as:
<LIST><PERSONID>12345</PERSONID><ADDITIONAL ADDRESS><ADDRESS><ADDRESS_TYPE>Home</ADDRESS_TYPE><STREET>123 Main </STREET><CITY>Montreal</CITY></ADDRESS><ADDRESS><ADDRESS_TYPE>Business</ADDRESS_TYPE><STREET>695 Fuller Ave</STREET><CITY>Montreal</CITY></ADDR
ESS><ADDITIONAL ADDRESS></LIST>
Tables:
CREATE TABLE [dbo].[LIST] (
[personid] [int] NULL ,
) ON [PRIMARY]
GO
CREATE TABLE [dbo].[ADDRESS] (
[personid] [int] NULL ,
[address_type] [char] (6) NULL,
[street] [char] (60) NULL ,
[city] [char] (50) NULL ,
) ON [PRIMARY]
GO
I tried the following schema, did not work. Any help would be greatly appreciated. Thanks.
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"
xmlns:sql="urn:schemas-microsoft-com:mapping-schema"><xsd:annotation><xsd:appinfo><sql:relation ship name="LIST_ADDITIONAL_ADDRESS" parent="LIST" parent-key="personid" child="ADDITIONAL_ADDRESS" child-key="personid"/><sql:relationship name="LIST_ADDITIONA
L_ADDRESS_ADDRESS" parent="LIST_ADDITIONAL_ADDRESS" parent-key="personid" child="ADDITIONAL_ADDRESS_ADDRESS" child-key="personid"/></xsd:appinfo></xsd:annotation><xsd:element name="LIST" sql:relation="LIST"><xsd:complexType><xsd:sequence ><xsd:element name
="personid" type="xsd:string" minOccurs="0" sql:field="personid"/><xsd:element name="LIST_ADDITIONAL_ADDRESS" minOccurs="0" maxOccurs="unbounded" sql:relation="ADDITIONAL_ADDRESS" sql:relationship="LIST_ADDITIONAL_ADDRESS"><xsd:co mplextType><xsd:sequence>
<xsd:element name="ADDRESS" minOccurs="0" maxOccurs="unbounded" sql:relation="ADDRESS" sql:relationship="LIST_ADDITIONAL_ADDRESS_ADDRESS" ><xsd:complexType><xsd:sequence><xsd:element name="address_type" type="xsd:string" minOccurs="0" sql:field="address_ty
pe"/><xsd:element name="street" type="xsd:string" minOccurs="0" sql:field="street"/><xsd:element name="city" type="xsd:string" minOccurs="0" sql:field="city"/></xsd:sequence></xsd:complexType></xsd:element></xsd:sequence><xsd:complextType><xsd:element></x
sd:sequence></xsd:complexType></element></xsd:schema>
Couple of things:
- I think you have an error at the end of your schema. You want to close
the complexType and element tags, not open new ones.
- I assume the "LIST_ADDITIONAL_ADDRESSES you refer to as the child in your
second relationship is the name of the first relatiionship? That doesn't
work. This can only refer to a table name.
- If all they did is add a wrapper element, can you use sql:is-constant?
--
Irwin Dolobowsky
Program Manager - SqlXml
This posting is provided "AS IS" with no warranties, and confers no rights.
"darren" <anonymous@.discussions.microsoft.com> wrote in message
news:C5C0A64D-7EDD-4E9C-AECC-4A609EEAEA7B@.microsoft.com...
>I am having a problem with an xsd design (again). The client has decided to
>make a change and everything I try does not work. They have ADDED a nested
>tag to a nested tag - a person can have multiple addresses. There is a
><PERSONID> tag that appears under the <LIST> tag at the same level as the
>new tags. I need the ADDRESS info to end up in an ADDRESS table, with the
>PERSONID populated. The tags appear as:
> <LIST><PERSONID>12345</PERSONID><ADDITIONAL
> ADDRESS><ADDRESS><ADDRESS_TYPE>Home</ADDRESS_TYPE><STREET>123 Main
> </STREET><CITY>Montreal</CITY></ADDRESS><ADDRESS><ADDRESS_TYPE>Business</ADDRESS_TYPE><STREET>695
> Fuller Ave</STREET><CITY>Montreal</CITY></ADDRESS><ADDITIONAL
> ADDRESS></LIST>
> Tables:
> CREATE TABLE [dbo].[LIST] (
> [personid] [int] NULL ,
> ) ON [PRIMARY]
> GO
> CREATE TABLE [dbo].[ADDRESS] (
> [personid] [int] NULL ,
> [address_type] [char] (6) NULL,
> [street] [char] (60) NULL ,
> [city] [char] (50) NULL ,
> ) ON [PRIMARY]
> GO
> I tried the following schema, did not work. Any help would be greatly
> appreciated. Thanks.
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"
> xmlns:sql="urn:schemas-microsoft-com:mapping-schema"><xsd:annotation><xsd:appinfo><sql:relation ship
> name="LIST_ADDITIONAL_ADDRESS" parent="LIST" parent-key="personid"
> child="ADDITIONAL_ADDRESS" child-key="personid"/><sql:relationship
> name="LIST_ADDITIONAL_ADDRESS_ADDRESS" parent="LIST_ADDITIONAL_ADDRESS"
> parent-key="personid" child="ADDITIONAL_ADDRESS_ADDRESS"
> child-key="personid"/></xsd:appinfo></xsd:annotation><xsd:element
> name="LIST"
> sql:relation="LIST"><xsd:complexType><xsd:sequence ><xsd:element
> name="personid" type="xsd:string" minOccurs="0"
> sql:field="personid"/><xsd:element name="LIST_ADDITIONAL_ADDRESS"
> minOccurs="0" maxOccurs="unbounded" sql:relation="ADDITIONAL_ADDRESS"
> sql:relationship="LIST_ADDITIONAL_ADDRESS"><xsd:co mplextType><xsd:sequence><xsd:element
> name="ADDRESS" minOccurs="0" maxOccurs="unbounded" sql:relation="ADDRESS"
> sql:relationship="LIST_ADDITIONAL_ADDRESS_ADDRESS" ><xsd:complexType><xsd:sequence><xsd:element
> name="address_type" type="xsd:string" minOccurs="0"
> sql:field="address_type"/><xsd:element name="street" type="xsd:string"
> minOccurs="0" sql:field="street"/><xsd:element name="city"
> type="xsd:string" minOccurs="0"
> sql:field="city"/></xsd:sequence></xsd:complexType></xsd:element></xsd:sequence><xsd:complextType><xsd:element></xsd:sequence></xsd:complexType></element></xsd:schema>
|||that worked, thanks a lot for your help.
|||Glad to help.
Irwin
Irwin Dolobowsky
Program Manager - SqlXml
This posting is provided "AS IS" with no warranties, and confers no rights.
"darren" <anonymous@.discussions.microsoft.com> wrote in message
news:62B6433B-C3CE-486F-B62A-C296D76BE433@.microsoft.com...
> that worked, thanks a lot for your help.