Dimension design question

Hi,

what is the best practice for design of large dimension, such as Order? In my scenario users want to analyze order intake using order status, issuer name and couple of other attributes, possibly even order number. We use fact dimension to accomplish that. Everything works, but I'm a bit concerned about performance. There are more than 10mil members in that dimension (and there is also invoicing dim as well, about the same size).

Is this the best design for this scenario? What if I create separate dimensions Issuer, Order Status ... and link them directly to the fact? Will the performance (though it's not bad now, I'm just thinking ahead) improve, and, most importantly, WHY? :)

Thanks.

Radim

What are your concerns about dimension performance?

You got to quite specific when you talk about performance. What is schenario for using your dimensions?

Do you expect users to drill down to the lowest level? Do you have nice natural hierarhies stucture into your dimension?

Analysis Services can nandle your multiple large dimensions. See referece to Project Real implemenation http://www.microsoft.com/sql/solutions/bi/projectreal.mspx

Building navigation paths using right set of native hierarchies is key to the dimension performance.

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

sql

Differential maintenance in plan sql 2000: setup

Hello!
I'm trying to setup a differential maintenance plan to backup all
users databases on sql 2000 using t-sql (or not)
I can't figure out or find how to include "all user databases" like i
would using a maintenance plan. This is a cake to do in sql 2005 but
sql 2000.... well lets just say :(There are maint plans in 2000, which you reach from the Maintenance Plans folder in EM. A 2000 maint
plan do not include diff backups, though.
Right-licking a db and select Backup and from there selecting Schedule do *not* create a maint plan.
So if you want to include stuff like naming the backup file with time stamp and deletion of old
backups, you have to do it yourself. There are plenty of code out there to get your started, for
instance below (2005, but adaptable for 2000):
http://www.karaszi.com/SQLServer/util_backup_script_like_MP.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"scottg" <scottgranado@.gmail.com> wrote in message
news:f9f653f3-f0c6-4cb8-ae3e-4694a380293f@.n58g2000hsf.googlegroups.com...
> Hello!
> I'm trying to setup a differential maintenance plan to backup all
> users databases on sql 2000 using t-sql (or not)
> I can't figure out or find how to include "all user databases" like i
> would using a maintenance plan. This is a cake to do in sql 2005 but
> sql 2000.... well lets just say :(

Different SQL Server Users on ASP.Net

Hi there,

When conecting to a MS SQL Server 2005, I could define in my connection string Windows Authentication.

What account it will be used? The one used by IIS (I still don't know the user ASP.net runs, if it is independent of IIS or not)?

And if I whant that some aspx pages have diferente acess rights? I need to use SQL Server Authentication with diferent users created in MS SQL Server right?

In ASP.net, what is best practice: Have one SQL account, and make users access rights in Business Logic, or have different SQL Accounts por the diferent access rights I whant in every page?

Sorry if this are basic questions, but In the find's I made, I saw very confusion ideas.

Thanks in advance, and sorry my english.

Alberto Ferreira

Hi Alberto,

ASP.NET runs under the ASPNET account (you can check under users to get more info about this account)

Unlike Client Server application. You dont have to follow the same logic in Web application.

You have to implement a Forms Authentication for authentication and implement GenericPrincipal containing IPrincipal and IIdentity for authorization.

In that you would create your Custom Screen Permission or Screen-Screen Action permission lookup table. You would find plenty of articles on this.

For connection pooling to take place the connection string has to be the same so in ASP.NET we reuse the same user name and password but we control the security at the application level than the database level which we previously used to do.

And never mind the english

Happy Programming

Anton

differences btween SQL Server and MSDE

Hi

I wonder what the differences between MSDE and SQL Server are. The main thing I'm conserned about is...

Are there any limit of concurrent users to the MSDE?

Regards

MM,

I believe the number of concurrent users in MSDE is limited to 5.

Zack|||This topic has been discussed many times on this Forum. For example, please see this post:view post 399794

Terri