Showing posts with label developing. Show all posts
Showing posts with label developing. Show all posts

Wednesday, March 7, 2012

Another database design issue help!

Hello all,
I am developing a web application and im in the middle of database design and facing a design issue. Here it is: A table for products a table for SizeChart (Small, Medium, Large) ColorChart (White, Ash, Yellow, Pink).
Each product is available in combination of different colors and size. Then product has images which are stored based on the selection from ColorChart table. I have created a table where many to many relation between product to color and size are related with primary key identity field for junction table too. I also have created a table tblProdImages with ProductID, ColorID, ImagePath fields
Here is the structure
Product ColorChart SizeChart
--- ---- ----
ProductID ColorID SizeID
Name ColorIcon Sybol

ProductColorSizeChart (junstcion table) ProductImages
------------ ------
ProductColorSizeID (Indentity) ProductImageID (Identity)
ProductID - FK ProductID - FK
ColorID - FK ColorID - FK
SizeID - FK ImagePathThumbnail
InStock ImagePathLarge
Offline

I have write DAL for product and managing junction table relation as collection in my product b/e object.
Here is my question
1- How effective this whole db schema is and how manageable is the relations, Suggest if any better solutions is.
2- Im facing updating problem in ProductDAL for updating collection items in database.
3- How can i manage and implement lazy loading in this scenario in my own written Data Access Layer.

Please clarify 'DAL' and 'b/e'|||1) The schema looks pretty good. The relationships look fairly straight forward and easy to maintain.
2 ) It would help if I had a better idea of what your Object Model & DAL look like.
3) It doesnt look like you have a situation where objects have amassive amount of data associated with them. Im not sureLazyLoading would be worth the trouble. Caching the objects andreturning references might be more useful for you.
|||Thanks Jeffrey for a prompt reply. First of all as far as b/e (business entity objects) are concerned they are blue print parent tables. As for relation btw product, color, size i have created a collection where each item is a structure having two fields for b/e of ColorInfo and SizeInfo (mapper of Color and Size tables). There is a possibility that a product may need to be added where this relation may not be applied as that product has no dependency of color and size so the collection will be empty and in DAL (Data Access Layer) class of product i have this check to determin the count of collection. If empty then Save method for relational entity objects will not be called.
I have implemented DAL code for saving relational object (Product,Color,Size) in product. Is it a right place?|||

asp.dude wrote:

Thanks Jeffrey for a prompt reply. First of allas far as b/e (business entity objects) are concerned theyare blue print parent tables. As for relation btw product, color, sizei have created a collection where each item is a structure havingtwo fields for b/e of ColorInfo and SizeInfo (mapper of Color and Sizetables). There is a possibility that a product may need to be addedwhere this relation may not be applied as that product has nodependency of color and size so the collection will be empty and in DAL(Data Access Layer) class of product i have this check to determin thecount of collection. If empty then Save method for relational entityobjects will not be called.
I have implemented DAL code for saving relational object (Product,Color,Size) in product. Is it a right place?


Thatsounds correct to me. I really couldnt tell you much more without seeing code.

Sunday, February 12, 2012

Analysis Services Help

I'm looking for some modest help in developing some MDX queries in Analysis Services against a datacube I've built.
Would anyone be willing to answer some specific e-mail on this? I am willing to provide a small honorarium for some timely help here.Unless there are disclosure issues you may have the best help from posting your questions here (Most likely, if you contact those who are most helpful, many will not refuse whatever you might wish to donate via paypal, etc.)?|||Originally posted by DBA
Unless there are disclosure issues you may have the best help from posting your questions here (Most likely, if you contact those who are most helpful, many will not refuse whatever you might wish to donate via paypal, etc.)?

I'm not too concerned about disclosure issues. I was mostly concerned about the detail involved. Providing enough context for someone to help me is going to be somewhat involved, and I'm not sure exactly what questions I need to ask. I was hoping for some assistance that might be a bit more iterative than is really practical (and perhaps appropriate) with a public web-based forum.

Given the suggestion, I'll try and work up a summary and sub-scenario and see if anyone is interested in helping (and perhaps helping more).

Thanks!

Analysis Services connexion problem using AMO via ASP.NET 2

Hi,

I've got a strange problem.
I'm developing an ASP.NET application connecting to an Analysis
Services 2005 database.

On my developpement PC I can run the web site virtually and my
connexion is ok. I can see all the databases running under my server.
BUT, when I deploy the site on the server, even if the connexion is a
success, I can't see any of my databases.

Concretly, the code looks like :

Dim oServeur As Microsoft.AnalysisServices.Server
oServeur = New Microsoft.AnalysisServices.Server
oServeur.Connect("ServerName") ' I do not type "(local)"

This part of the code is ok both on developpement and server side.

But If I add this :

My.Response.Write(oServeur.DataBases.Count)

The response is "2" on application developpement side and
"0" on the server side ...

Can someone help me please ?

This very much looks like the permissions problem. Check the security under which your ASP application is running. Check the security on the virtual directory for your application.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Analysis Services connexion problem using AMO via ASP.NET 2

Hi,

I've got a strange problem.
I'm developing an ASP.NET application connecting to an Analysis
Services 2005 database.

On my developpement PC I can run the web site virtually and my
connexion is ok. I can see all the databases running under my server.
BUT, when I deploy the site on the server, even if the connexion is a
success, I can't see any of my databases.

Concretly, the code looks like :

Dim oServeur As Microsoft.AnalysisServices.Server
oServeur = New Microsoft.AnalysisServices.Server
oServeur.Connect("ServerName") ' I do not type "(local)"

This part of the code is ok both on developpement and server side.

But If I add this :

My.Response.Write(oServeur.DataBases.Count)

The response is "2" on application developpement side and
"0" on the server side ...

Can someone help me please ?

This very much looks like the permissions problem. Check the security under which your ASP application is running. Check the security on the virtual directory for your application.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Thursday, February 9, 2012

Analysis Services 64-bit clustering

In an article in another usenet group, a few months ago, it was
mentioned that MS were developing an updated document for the steps to
cluster the 64-bit
version of Analysis Services.
I'm the tech lead in one of my countries first implementations of
64-bit SQL,
and this has been an issue for us. We've put time into getting the
clustering going, but didn't want to proceed to far down the path
until MS released a supported procedure.
Can anyone tell me if this document has been finalised, and if so when
it will be released?
Cheers,
Reece.
Post a follow
Reece,
A knowledge base article has been written for the clustering Analysis Services 64-bit. Currently it is being reviewed. I don't know when it will become public. I am trying to find out the release date.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Reece,
Guess what? The KB is public today. Here is the link
How to cluster SQL Server 2000 Analysis Services in Windows 2000 and Windows Server 2003
http://support.microsoft.com/?kbid=308023
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Uttam,
Thanks for this, but I've already seen this article. I'm after one
which explains how to do the clustering with 64-bit Analysis Services.
As this uses SQL Server instead of an Access mdb.
I could get this done myself most likely, but it would involve
registry hacking, and I would rather have a step by step outline from
MS first. Especially when this is for a client site and I need to have
MS support if things go wrong. Which I doubt would be the case when I
tell them I hacked the registry to get this clustering working.
Cheers,
Reece.
uttamkp@.online.microsoft.com (Uttam Parui[MS]) wrote in message news:<dUcw#Z0aEHA.2924@.cpmsftngxa06.phx.gbl>...
> Reece,
> Guess what? The KB is public today. Here is the link
> How to cluster SQL Server 2000 Analysis Services in Windows 2000 and Windows Server 2003
> http://support.microsoft.com/?kbid=308023
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
|||I am currently working the responsible parties in Microsoft to have the KB updated for 64 bit.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||here are the steps that worked for me. Use public documnet
http://support.microsoft.com/default...b;en-us;308023
Add the following steps
Replace the 32bit steps for "Install Anlysis Services on Node 1" with:
1) Make sure a virutual instance of SQL server 64bit is already installed
and clustered.
2) run setup.exe
3) click "Start a New Installation", Click "Local Instance" and then "next"
4) Click "next" twice
5) Clear the SQL server check box so that only Analysis services will eb
installed
6) Click "data Files" and change the location to a Clustered drive to be
used by Analysis Services
7) Under Instance Name type in the name of a SQL server instance to be used
by Analysis Services 64 bit. You will have to do the same on Node to so pick
2 slightly different name like ASInstance-A that way on the second one you
will have ASInstance-B
8) Take the defaults for the rest
For the steps "Move the Analsysis Services Query Log Database"
1) log on to the local instance of SQL you created on Node 1
2) move the following DB OLAPQueryLog to the Virutal instance of SQL. Make
sure the Database files are on one of the Clustered drives the virutual
instance SQL can access.
For "install Anlysis Services on Node2"
Follow the steps for "installing Analysis Services on Node 1" above
Move the OlapRepository DB from the local instance on Node 2 to the Virutual
SQL instance. Make sure the DB files reside on a drive the Virtual instance
of SQL can access.
For the section called "modify the registry Keys for the analysis server on
Node 2"
- 64 bit changes for steps 1-4
1) Run the analysis services manager on a 32 bit client. Type in the name
of the local SQL server instance on Node 1 (it does not matter if SQL or
Analysis Services is running)
2) Right-click the server name, click "modify repository Connection String"
3) change the portion of the string for "Source=" to reflect the name of
your Virtual SQL server
- 64 bit changes for Step 5
1) change the location to the same drive letter where you stored the
OLAPQueryLog and OLAPRepository DB files.
- 64 bit changes for steps 7 and 8
1) change the portion of the string for "Source=" to reflect the name of
your Virtual SQL server
- 64 bit additional steps (Otherwise your AS data will be stored on the loca
C drive of one of the nodes and will not be avaialable to the cluster.
1) Connect to the registry Key
HKLM\Software\Microsoft\OLAPSERVER\Currentversion
2) Change the values of the following keys to reflect the drive letter where
you stored the OLAPQueryLog and OLAPRepository DB files
RootDir
RootDir:Default
TempDirectory
TempDirectory:Default.
- Repeat all steps for Node 2
"Reece" wrote:

> Uttam,
> Thanks for this, but I've already seen this article. I'm after one
> which explains how to do the clustering with 64-bit Analysis Services.
> As this uses SQL Server instead of an Access mdb.
> I could get this done myself most likely, but it would involve
> registry hacking, and I would rather have a step by step outline from
> MS first. Especially when this is for a client site and I need to have
> MS support if things go wrong. Which I doubt would be the case when I
> tell them I hacked the registry to get this clustering working.
> Cheers,
> Reece.
>
> uttamkp@.online.microsoft.com (Uttam Parui[MS]) wrote in message news:<dUcw#Z0aEHA.2924@.cpmsftngxa06.phx.gbl>...
>
|||here are the steps that worked for me. Use public documnet
http://support.microsoft.com/default...b;en-us;308023
Add the following steps
Replace the 32bit steps for "Install Anlysis Services on Node 1" with:
1) Make sure a virutual instance of SQL server 64bit is already installed
and clustered.
2) run setup.exe
3) click "Start a New Installation", Click "Local Instance" and then "next"
4) Click "next" twice
5) Clear the SQL server check box so that only Analysis services will eb
installed
6) Click "data Files" and change the location to a Clustered drive to be
used by Analysis Services
7) Under Instance Name type in the name of a SQL server instance to be used
by Analysis Services 64 bit. You will have to do the same on Node to so pick
2 slightly different name like ASInstance-A that way on the second one you
will have ASInstance-B
8) Take the defaults for the rest
For the steps "Move the Analsysis Services Query Log Database"
1) log on to the local instance of SQL you created on Node 1
2) move the following DB OLAPQueryLog to the Virutal instance of SQL. Make
sure the Database files are on one of the Clustered drives the virutual
instance SQL can access.
For "install Anlysis Services on Node2"
Follow the steps for "installing Analysis Services on Node 1" above
Move the OlapRepository DB from the local instance on Node 2 to the Virutual
SQL instance. Make sure the DB files reside on a drive the Virtual instance
of SQL can access.
For the section called "modify the registry Keys for the analysis server on
Node 2"
- 64 bit changes for steps 1-4
1) Run the analysis services manager on a 32 bit client. Type in the name
of the local SQL server instance on Node 1 (it does not matter if SQL or
Analysis Services is running)
2) Right-click the server name, click "modify repository Connection String"
3) change the portion of the string for "Source=" to reflect the name of
your Virtual SQL server
- 64 bit changes for Step 5
1) change the location to the same drive letter where you stored the
OLAPQueryLog and OLAPRepository DB files.
- 64 bit changes for steps 7 and 8
1) change the portion of the string for "Source=" to reflect the name of
your Virtual SQL server
- 64 bit additional steps (Otherwise your AS data will be stored on the loca
C drive of one of the nodes and will not be avaialable to the cluster.
1) Connect to the registry Key
HKLM\Software\Microsoft\OLAPSERVER\Currentversion
2) Change the values of the following keys to reflect the drive letter where
you stored the OLAPQueryLog and OLAPRepository DB files
RootDir
RootDir:Default
TempDirectory
TempDirectory:Default.
- Repeat all steps for Node 2
"Uttam Parui[MS]" wrote:

> I am currently working the responsible parties in Microsoft to have the KB updated for 64 bit.
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>