Ask limitation about SQL server

Hi, Any one can tell me is it true that
The SQL Server in Windows Small Business Server 2003 Premium Edition have a limitation on building a database can not bigger than 10G. It is difficult to find such info. in MS web site
Please help, thanks a lot
TONo, SBS has the same size limitation as SQL Server 2000 (~1 million TB).
However, you are limited to two physical processors and 4 GB RAM.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"TO" <anonymous@.discussions.microsoft.com> wrote in message
news:E5355930-B0C9-434A-B77F-2CA80676D995@.microsoft.com...
> Hi, Any one can tell me is it true that:
> The SQL Server in Windows Small Business Server 2003 Premium Edition have
a limitation on building a database can not bigger than 10G. It is difficult
to find such info. in MS web site.
> Please help, thanks a lot.
> TO|||I only got as far as 475,000 TB and my machine choked.
LOL.
James Hokes
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%230bO5oz$DHA.2348@.TK2MSFTNGP09.phx.gbl...
> No, SBS has the same size limitation as SQL Server 2000 (~1 million TB).
> However, you are limited to two physical processors and 4 GB RAM.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "TO" <anonymous@.discussions.microsoft.com> wrote in message
> news:E5355930-B0C9-434A-B77F-2CA80676D995@.microsoft.com...
> > Hi, Any one can tell me is it true that:
> > The SQL Server in Windows Small Business Server 2003 Premium Edition
have
> a limitation on building a database can not bigger than 10G. It is
difficult
> to find such info. in MS web site.
> > Please help, thanks a lot.
> >
> > TO
>

Ask limitation about SQL server

Hi, Any one can tell me is it true that:
The SQL Server in Windows Small Business Server 2003 Premium Edition have a
limitation on building a database can not bigger than 10G. It is difficult t
o find such info. in MS web site.
Please help, thanks a lot.
TONo, SBS has the same size limitation as SQL Server 2000 (~1 million TB).
However, you are limited to two physical processors and 4 GB RAM.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"TO" <anonymous@.discussions.microsoft.com> wrote in message
news:E5355930-B0C9-434A-B77F-2CA80676D995@.microsoft.com...
> Hi, Any one can tell me is it true that:
> The SQL Server in Windows Small Business Server 2003 Premium Edition have
a limitation on building a database can not bigger than 10G. It is difficult
to find such info. in MS web site.
> Please help, thanks a lot.
> TO|||I only got as far as 475,000 TB and my machine choked.
LOL.
James Hokes
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%230bO5oz$DHA.2348@.TK2MSFTNGP09.phx.gbl...
> No, SBS has the same size limitation as SQL Server 2000 (~1 million TB).
> However, you are limited to two physical processors and 4 GB RAM.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "TO" <anonymous@.discussions.microsoft.com> wrote in message
> news:E5355930-B0C9-434A-B77F-2CA80676D995@.microsoft.com...
have
> a limitation on building a database can not bigger than 10G. It is
difficult
> to find such info. in MS web site.
>

AS 2005: Where are Parallel Period calculations in the Business Intelligence Wizard

I am using the July CTP of SQL Server 2005.

Books Online indicates that the Business Intelligence Wizard in the BI Development Studio supports parallel period calculations. I did not see this class of calculations in the list.

The available calculations were Year to Date, Quarter to Date, Month to Date, Twelve Months to Date, Twelve Month Moving Average, Six Month Moving Average, Three Month Moving Average, Year Over Year Growth, Year Over Year Growth %, Quarter Over Quarter Growth, Quarter Over Quarter Growth %, Month Over Month Growth, Month Over Month Growth %, Day Over Day Growth, Day Over Day Growth %. I would have expected calculations like "Period Prior Year" or "Prior Period"

Is there something special I need to do to make the parallel period calculations available? Or are they just not yet available in the July CTP?Kendal,

When BOL states "Parallel period comparisons", it is referring to the "... Growth" and "... Growth %" calculations that are available. For example, the "Year Over Year Growth" calculation will return the difference between measures for a period in one year compared to the same period in the prior year (whether the period selected is a quarter, month, week, or day).

Let me know if that is not the type of parallel period calculations you are wanting...

Dave Fackler
|||

You have clarified it for me.

I had previously created and used more direct period calculated measures like "Value in prior period" or "Value for same period in prior year". I expected to see those as well. But we can create those on our own based on the provided templates.

Thanks for the response!

AS 2005 Business Intelligence Wizard scripts

In Analysis Services 2005, using the Business Intelligence Wizard in the BI Development Studio to add time calculations to a cube worked fine when only base measures are included in the scope. When a calculated measure is added to the scope of the Business Intelligence Wizard time calculation, all that is returned for the Business Intelligence Wizard time calculation value is “NA”. What could be the problem/how can I make this work correctly?

The exact same time calculation was being created by the Business Intelligence Wizard - the only difference was adding one calculated measure to the scope. Could this have anything to do with pass and solve order? Do the measures that the calculated measure depends on also have to be listed in the scope for the BI Development Studio time calculation? I'm sort of reaching here.

Any help is appreciated,
Dan

Dan,

There are two separate issues, both of which have been fixed for the next CTP:

1. A redundant scope is created when both physical and calculated measures are chosen.
2. Seeing NA in the context of calculated measures.

The only *possible* workaround I know of for issue 2 is to edit the MDX script and replace the AGGREGATE function with SUM, but this should only be done if you are postive that it makes sense to sum the measures in question. Applying this change may then cause you to hit issue 1, at which point you would, if needed, want to remove the first (outer scope) and move those physical measures into the inline scopes (on the left hand side of the '=').

-rob|||Thanks for the thorough explanation. I will attempt to apply the solution(s).

Dan
|||Is a CTP planned between now and the final release?|||Yes, there will be another CTP released in the near future.

-rob

AS 2005 Business Intelligence Wizard - rerunning to add time calculations

In Analysis Services 2005, once you’ve used the Business Intelligence Wizard in the BI Development Studio to add time calculations to a cube, how do you come back later and add additional standard time calculations based on the named calculation that was already created in the cube’s data source view by the prior run of the Wizard?Kendal,

Assuming I understand you correctly, you want to add additional custom time calculations after running the Time Intelligence wizard...

The wizard creates a calculated column in your time dimension table within the DSV. It then adds a new attribute hierarchy to your time dimension based on this new attribute. This serves as an "holding point" for the calculations. It then creates the calculations you selected in the calculations script for the cube, using the following steps:

- it starts the calcuations by adding new members to the attribute hierarchy with a default value of "NA"
- the script then uses a "scope" statement to scope the calculations to the measures you selected in the wizard
- each of the calculations you selected by the wizard are then implemented by using an MDX expression to define the values of the new calculated member across the time hierarchy the calculations apply to
- finally, an "end scope" statement closes things out

If you review the calculation script for the cube, you should see this at the end of the script after running the Time Intelligence wizard.

To add new custom calculations to the same attribute hierarchy created by the wizard, you can just add new calculated members to the hierarchy and add the custom MDX expressions needed. To add a new member, simply add a new "Create Member" statement before the "scope" statement, using the same syntax and construction as the ones added by the wizard. Then, add a new calculation after the "scope" statement that specifies the MDX expression that should be used to calculate values for the new calculated member. Use a syntax similar to that used for the existing calculations.

You should note that any calculated members that you add in this manner will be restricted to the same scope as the ones added by the wizard -- meaning the calculated member will only return values for the same list of members selected in the wizard. You can use variations of this technique with your own scope statements to change this.

Hope this helps and is understandable :-)

Dave Fackler
|||It does help. I had been thinking of the wizard as more of a development tool that would allow me to iteratively refine my cube. However, at this point in time, it serves more to codify best practices and generate examples of how to implement certain features in the context of the cube.

As is, it certainly is a big benefit.

Thanks for the clarification.|||

Hi Dave

I have tried to 'add time intelligence' but when I browse the result I only get something in 'current time'. In 'year to date' I only get the value 'N/A'

On my calculations I have nothing in my 'parent hierarchies' . On the parent hierarchies i got an error

the specified hierarchy [Time].[Year - Quarter - Month - Date Time Calculations] does not exist int the cube.

Scope(

{

[Measures].[Invoice Net Sales Amt]

}

)

( [Time].[Year - Quarter - Month - Date Time Calculations].[Quarter to Date],

[Time].[Quarter].[Quarter].Members ) =

Aggregate(

{ [Time].[Year - Quarter - Month - Date Time Calculations].DefaultMember } *

PeriodsToDate(

[Time].[Year - Quarter - Month - Date].[QuarterName],

[Time].[Year - Quarter - Month - Date].CurrentMember

)

)

End Scope

|||

Some of the calculations produced by the Time Intelligence Wizard, including the Year to Date ones, don't work - see
http://spaces.msn.com/cwebbbi/blog/cns!7B84B0F2C239489A!379.entry

Hopefully this will be fixed in SP1.

Chris

|||

I'm running SP1 on Standard Edition. I'm also using the code (below) that's recommended as a workaround but still get the same problem. NAs are displayed when I try to browse the data for this measure / calculation combo. All I've done is put the code into my calculations script on Adventure Works. Current Date (which I assume is a hidden calculation) works.

Is there any other issue that could be causing this or is there something I've missed? Any help on this would be much appreciated.

Create Member

CurrentCube.[Date].[Fiscal Date Calculations].[Year to Date]

As "NA" ;

Scope(

{

[Measures].[Internet Sales Amount],

[Measures].[Reseller Sales Amount]

}

);

( [Date].[Fiscal Date Calculations].[Year to Date],

[Date].[Fiscal Year].[Fiscal Year].Members ) =

Aggregate(

{ [Date].[Fiscal Date Calculations].DefaultMember } *

PeriodsToDate(

[Date].[Fiscal].[Fiscal Year],

[Date].[Fiscal].CurrentMember

)

) ;

AS 2005 Business Intelligence Wizard - rerunning to add time calculations

In Analysis Services 2005, once you’ve used the Business Intelligence Wizard in the BI Development Studio to add time calculations to a cube, how do you come back later and add additional standard time calculations based on the named calculation that was already created in the cube’s data source view by the prior run of the Wizard?Kendal,

Assuming I understand you correctly, you want to add additional custom time calculations after running the Time Intelligence wizard...

The wizard creates a calculated column in your time dimension table within the DSV. It then adds a new attribute hierarchy to your time dimension based on this new attribute. This serves as an "holding point" for the calculations. It then creates the calculations you selected in the calculations script for the cube, using the following steps:

- it starts the calcuations by adding new members to the attribute hierarchy with a default value of "NA"
- the script then uses a "scope" statement to scope the calculations to the measures you selected in the wizard
- each of the calculations you selected by the wizard are then implemented by using an MDX expression to define the values of the new calculated member across the time hierarchy the calculations apply to
- finally, an "end scope" statement closes things out

If you review the calculation script for the cube, you should see this at the end of the script after running the Time Intelligence wizard.

To add new custom calculations to the same attribute hierarchy created by the wizard, you can just add new calculated members to the hierarchy and add the custom MDX expressions needed. To add a new member, simply add a new "Create Member" statement before the "scope" statement, using the same syntax and construction as the ones added by the wizard. Then, add a new calculation after the "scope" statement that specifies the MDX expression that should be used to calculate values for the new calculated member. Use a syntax similar to that used for the existing calculations.

You should note that any calculated members that you add in this manner will be restricted to the same scope as the ones added by the wizard -- meaning the calculated member will only return values for the same list of members selected in the wizard. You can use variations of this technique with your own scope statements to change this.

Hope this helps and is understandable :-)

Dave Fackler
|||It does help. I had been thinking of the wizard as more of a development tool that would allow me to iteratively refine my cube. However, at this point in time, it serves more to codify best practices and generate examples of how to implement certain features in the context of the cube.

As is, it certainly is a big benefit.

Thanks for the clarification.|||

Hi Dave

I have tried to 'add time intelligence' but when I browse the result I only get something in 'current time'. In 'year to date' I only get the value 'N/A'

On my calculations I have nothing in my 'parent hierarchies' . On the parent hierarchies i got an error

the specified hierarchy [Time].[Year - Quarter - Month - Date Time Calculations] does not exist int the cube.

Scope(

{

[Measures].[Invoice Net Sales Amt]

}

)

( [Time].[Year - Quarter - Month - Date Time Calculations].[Quarter to Date],

[Time].[Quarter].[Quarter].Members ) =

Aggregate(

{ [Time].[Year - Quarter - Month - Date Time Calculations].DefaultMember } *

PeriodsToDate(

[Time].[Year - Quarter - Month - Date].[QuarterName],

[Time].[Year - Quarter - Month - Date].CurrentMember

)

)

End Scope

|||

Some of the calculations produced by the Time Intelligence Wizard, including the Year to Date ones, don't work - see
http://spaces.msn.com/cwebbbi/blog/cns!7B84B0F2C239489A!379.entry

Hopefully this will be fixed in SP1.

Chris

|||

I'm running SP1 on Standard Edition. I'm also using the code (below) that's recommended as a workaround but still get the same problem. NAs are displayed when I try to browse the data for this measure / calculation combo. All I've done is put the code into my calculations script on Adventure Works. Current Date (which I assume is a hidden calculation) works.

Is there any other issue that could be causing this or is there something I've missed? Any help on this would be much appreciated.

Create Member

CurrentCube.[Date].[Fiscal Date Calculations].[Year to Date]

As "NA" ;

Scope(

{

[Measures].[Internet Sales Amount],

[Measures].[Reseller Sales Amount]

}

);

( [Date].[Fiscal Date Calculations].[Year to Date],

[Date].[Fiscal Year].[Fiscal Year].Members ) =

Aggregate(

{ [Date].[Fiscal Date Calculations].DefaultMember } *

PeriodsToDate(

[Date].[Fiscal].[Fiscal Year],

[Date].[Fiscal].CurrentMember

)

) ;

AS 2005 Business Intelligence Wizard - rerunning to add time calculations

In Analysis Services 2005, once you’ve used the Business Intelligence Wizard in the BI Development Studio to add time calculations to a cube, how do you come back later and add additional standard time calculations based on the named calculation that was already created in the cube’s data source view by the prior run of the Wizard?Kendal,

Assuming I understand you correctly, you want to add additional custom time calculations after running the Time Intelligence wizard...

The wizard creates a calculated column in your time dimension table within the DSV. It then adds a new attribute hierarchy to your time dimension based on this new attribute. This serves as an "holding point" for the calculations. It then creates the calculations you selected in the calculations script for the cube, using the following steps:

- it starts the calcuations by adding new members to the attribute hierarchy with a default value of "NA"
- the script then uses a "scope" statement to scope the calculations to the measures you selected in the wizard
- each of the calculations you selected by the wizard are then implemented by using an MDX expression to define the values of the new calculated member across the time hierarchy the calculations apply to
- finally, an "end scope" statement closes things out

If you review the calculation script for the cube, you should see this at the end of the script after running the Time Intelligence wizard.

To add new custom calculations to the same attribute hierarchy created by the wizard, you can just add new calculated members to the hierarchy and add the custom MDX expressions needed. To add a new member, simply add a new "Create Member" statement before the "scope" statement, using the same syntax and construction as the ones added by the wizard. Then, add a new calculation after the "scope" statement that specifies the MDX expression that should be used to calculate values for the new calculated member. Use a syntax similar to that used for the existing calculations.

You should note that any calculated members that you add in this manner will be restricted to the same scope as the ones added by the wizard -- meaning the calculated member will only return values for the same list of members selected in the wizard. You can use variations of this technique with your own scope statements to change this.

Hope this helps and is understandable :-)

Dave Fackler
|||It does help. I had been thinking of the wizard as more of a development tool that would allow me to iteratively refine my cube. However, at this point in time, it serves more to codify best practices and generate examples of how to implement certain features in the context of the cube.

As is, it certainly is a big benefit.

Thanks for the clarification.|||

Hi Dave

I have tried to 'add time intelligence' but when I browse the result I only get something in 'current time'. In 'year to date' I only get the value 'N/A'

On my calculations I have nothing in my 'parent hierarchies' . On the parent hierarchies i got an error

the specified hierarchy [Time].[Year - Quarter - Month - Date Time Calculations] does not exist int the cube.

Scope(

{

[Measures].[Invoice Net Sales Amt]

}

)

( [Time].[Year - Quarter - Month - Date Time Calculations].[Quarter to Date],

[Time].[Quarter].[Quarter].Members ) =

Aggregate(

{ [Time].[Year - Quarter - Month - Date Time Calculations].DefaultMember } *

PeriodsToDate(

[Time].[Year - Quarter - Month - Date].[QuarterName],

[Time].[Year - Quarter - Month - Date].CurrentMember

)

)

End Scope

|||

Some of the calculations produced by the Time Intelligence Wizard, including the Year to Date ones, don't work - see
http://spaces.msn.com/cwebbbi/blog/cns!7B84B0F2C239489A!379.entry

Hopefully this will be fixed in SP1.

Chris

|||

I'm running SP1 on Standard Edition. I'm also using the code (below) that's recommended as a workaround but still get the same problem. NAs are displayed when I try to browse the data for this measure / calculation combo. All I've done is put the code into my calculations script on Adventure Works. Current Date (which I assume is a hidden calculation) works.

Is there any other issue that could be causing this or is there something I've missed? Any help on this would be much appreciated.

Create Member

CurrentCube.[Date].[Fiscal Date Calculations].[Year to Date]

As "NA" ;

Scope(

{

[Measures].[Internet Sales Amount],

[Measures].[Reseller Sales Amount]

}

);

( [Date].[Fiscal Date Calculations].[Year to Date],

[Date].[Fiscal Year].[Fiscal Year].Members ) =

Aggregate(

{ [Date].[Fiscal Date Calculations].DefaultMember } *

PeriodsToDate(

[Date].[Fiscal].[Fiscal Year],

[Date].[Fiscal].CurrentMember

)

) ;