Industry standard data warehouse models

Are there any resources for industry standard data warehouse models? I'm especially interested in financial models regarding securities (stocks, commodities, etc.).

Are you looking for data models in general?

Or are you looking for designs of data mining models that fit a particular schema?

|||

Both! Rather than reinvent the wheel, it would be nice if such resources existed.

However, my current project regards the securities markets in particular.

|||I'm going to move this thread to the OLAP forum where you may find a better audience to answer about data models. Once you get a data model, then it's easier to talk about data mining (at least from where you're starting)|||Where's the OLAP forum? I thought Analysis Services was the place to ask OLAP questions.|||

Take a look at the Kimball group http://www.kimballgroup.com/

See if you can find datawarehousing model you are looking for.

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

INDEXING A VIEW in MSSQL2K5x64.de Standard w.SP1 ... ERROR 1939

I'm experiencing a problem while trying to index a view ... I'm using a single field and everything else are default entry's. I'm getting the Error Message 1939 .

The code is a follows:

USE [CS_WGO]

GO

SET ARITHABORT ON

GO

SET CONCAT_NULL_YIELDS_NULL ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_NULLS ON

GO

SET ANSI_PADDING ON

GO

SET ANSI_WARNINGS ON

GO

SET NUMERIC_ROUNDABORT OFF

GO

CREATE UNIQUE CLUSTERED INDEX [IDX_ALG_ORG_BEZ_V_1] ON [dbo].[ALG_ORG_BEZ_V]

(

[NDL] ASC

)WITH (STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = OFF) ON [PRIMARY]

GO

And the Error is:

Msg 1939, Level 16, State 1, Line 1

Index kann für die 'ALG_ORG_BEZ_V'-Sicht nicht erstellt werden, da die Sicht nicht schemagebunden ist.

For those of you who do not read German ... it means something like ..." The Index kann not be created because the view is not bound to a schema.

I don't understand what that means for me ... can someone explain that to me a little bit more in depth ... ?

Thanx ... wvg

I m facing the same problem when tried with interface of sqlserver 2005 and the database was sql server 2000, how to get rid of it as i wish to decrease the exectuion time of the view. and so tried to index it.

|||

can anyone please help me with this please?

thanks

|||

can u post the schema (script) of the view. to create index on a view (indexed view) there are lot of rules to be followed. One of the requirement is to have the view Schema bound. ie the View script should have a SCHEMABINDING clause. Read about this in BOL Create View section.

Madhu

INDEXING A VIEW in MSSQL2K5x64.de Standard w.SP1 ... ERROR 1939

I'm experiencing a problem while trying to index a view ... I'm using a single field and everything else are default entry's. I'm getting the Error Message 1939 .

The code is a follows:

USE [CS_WGO]

GO

SET ARITHABORT ON

GO

SET CONCAT_NULL_YIELDS_NULL ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_NULLS ON

GO

SET ANSI_PADDING ON

GO

SET ANSI_WARNINGS ON

GO

SET NUMERIC_ROUNDABORT OFF

GO

CREATE UNIQUE CLUSTERED INDEX [IDX_ALG_ORG_BEZ_V_1] ON [dbo].[ALG_ORG_BEZ_V]

(

[NDL] ASC

)WITH (STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = OFF) ON [PRIMARY]

GO

And the Error is:

Msg 1939, Level 16, State 1, Line 1

Index kann für die 'ALG_ORG_BEZ_V'-Sicht nicht erstellt werden, da die Sicht nicht schemagebunden ist.

For those of you who do not read German ... it means something like ..." The Index kann not be created because the view is not bound to a schema.

I don't understand what that means for me ... can someone explain that to me a little bit more in depth ... ?

Thanx ... wvg

I m facing the same problem when tried with interface of sqlserver 2005 and the database was sql server 2000, how to get rid of it as i wish to decrease the exectuion time of the view. and so tried to index it.

|||

can anyone please help me with this please?

thanks

|||

can u post the schema (script) of the view. to create index on a view (indexed view) there are lot of rules to be followed. One of the requirement is to have the view Schema bound. ie the View script should have a SCHEMABINDING clause. Read about this in BOL Create View section.

Madhu

INDEXING A VIEW in MSSQL2K5x64.de Standard w.SP1 ... ERROR 1939

I'm experiencing a problem while trying to index a view ... I'm using a single field and everything else are default entry's. I'm getting the Error Message 1939 .

The code is a follows:

USE [CS_WGO]

GO

SET ARITHABORT ON

GO

SET CONCAT_NULL_YIELDS_NULL ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_NULLS ON

GO

SET ANSI_PADDING ON

GO

SET ANSI_WARNINGS ON

GO

SET NUMERIC_ROUNDABORT OFF

GO

CREATE UNIQUE CLUSTERED INDEX [IDX_ALG_ORG_BEZ_V_1] ON [dbo].[ALG_ORG_BEZ_V]

(

[NDL] ASC

)WITH (STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = OFF) ON [PRIMARY]

GO

And the Error is:

Msg 1939, Level 16, State 1, Line 1

Index kann für die 'ALG_ORG_BEZ_V'-Sicht nicht erstellt werden, da die Sicht nicht schemagebunden ist.

For those of you who do not read German ... it means something like ..." The Index kann not be created because the view is not bound to a schema.

I don't understand what that means for me ... can someone explain that to me a little bit more in depth ... ?

Thanx ... wvg

I m facing the same problem when tried with interface of sqlserver 2005 and the database was sql server 2000, how to get rid of it as i wish to decrease the exectuion time of the view. and so tried to index it.

|||

can anyone please help me with this please?

thanks

|||

can u post the schema (script) of the view. to create index on a view (indexed view) there are lot of rules to be followed. One of the requirement is to have the view Schema bound. ie the View script should have a SCHEMABINDING clause. Read about this in BOL Create View section.

Madhu

Indexed Views in Enterprise Edition...?

We are using SQL Server 2000 Standard Edition. Among other things, the
"Enterprise" edition adds "indexed views".
Could someone tell me what indexed views are, and what they are good for?
Is this simply an index on a view? Do the underlying tables have to be
static for the index to be effective? Pros/cons?
Thanks!!"JM" <JM@.nospam.com> wrote in message
news:%23F5n2tjEGHA.140@.TK2MSFTNGP12.phx.gbl...
> We are using SQL Server 2000 Standard Edition. Among other things, the
> "Enterprise" edition adds "indexed views".
> Could someone tell me what indexed views are, and what they are good for?
> Is this simply an index on a view? Do the underlying tables have to be
> static for the index to be effective? Pros/cons?
> Thanks!!
>
The BOL has a pretty decent description. Search for the following:
"Designing an Indexed View"
Rick Sawtell
MCT, MCSD, MCDBA|||Also, take a look at this white paper:
http://www.microsoft.com/technet/pr.../ipsql05iv.mspx
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Rick Sawtell" <Quickening@.msn.com> wrote in message
news:%230XpE0jEGHA.2040@.TK2MSFTNGP14.phx.gbl...
> "JM" <JM@.nospam.com> wrote in message
> news:%23F5n2tjEGHA.140@.TK2MSFTNGP12.phx.gbl...
> The BOL has a pretty decent description. Search for the following:
> "Designing an Indexed View"
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||Indexed views are also available in other SQL Server editions. However, in
Enterprise Edition, indexes on views are automatically considered by the
optimizer and even when the view is not referenced. A NOEXPAND hint is
needed to use view indexes in other editions.
The Books Online describes indexed views in much more detail than can be
discussed here but a short answer is that view indexes contain data
materialized from the underlying tables. This redundant data is
automatically maintained by SQL Server as the underlying data changes.
Consequently, data is dynamic rather than static.
Indexed views are especially nice for aggregated data and can also be used
to avoid complex joins. This can significantly reduce the work needed to
retrieve data by reporting applications with large data volumes. The
downsides are that there are many restrictions on using indexed views (see
BOL) and additional overhead is needed to maintain the view index(es). In
my experience, indexed views may be appropriate for reporting databases but
need to be used carefully in OLTP apps.
Hope this helps.
Dan Guzman
SQL Server MVP
"JM" <JM@.nospam.com> wrote in message
news:%23F5n2tjEGHA.140@.TK2MSFTNGP12.phx.gbl...
> We are using SQL Server 2000 Standard Edition. Among other things, the
> "Enterprise" edition adds "indexed views".
> Could someone tell me what indexed views are, and what they are good for?
> Is this simply an index on a view? Do the underlying tables have to be
> static for the index to be effective? Pros/cons?
> Thanks!!
>