Larger Scale SSAS 2005 deployment configuration options...

I'm wondering if there is anything like

Microsoft SQL Server 2000 Analysis Services Operations Guide.doc

Microsoft SQL Server 2000 Analysis Services Performance Guide.doc

for SSAS 2005. I'm working on a 22 Gig cube (that is size with no aggs) with a 32-Gig RAM Server and want to do more tuning - I should be able to get the whole thing in RAM, no? Shouldn't that make it really fast? I'm particularly interested in all of the Analysis Services Properties for SSAS.

What does "-3000" mean for several of the properties? I was thinking that raising many of the max RAM settings could be good, but if they are based on percentages, then that would scale with the server and wouldn't need tuning. There seems to be extremely little info. I see the basic info on 3 or 4 of the RAM settings with the percentages, I want much more than that.

I've looked around and read/skimmed 3 books, but few go into how to deploy to 32 Gigs of RAM / 8 processors and get the best use of the system...

So I'm looking either for direction on a paper or book I've missed or for specific help - both are good. Feel free to mention property changes you've implemented and that worked for you here!

Some information for you:

Server configuration properties docuement is found here: http://download.microsoft.com/download/4/f/8/4f8f2dc9-a9a7-4b68-98cb-163482c95e0b/SSASProperties.doc

Project REAL implementation references have a lot of useful information: http://www.microsoft.com/sql/solutions/bi/projectreal.mspx

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

Large scale databases - common practice

Hi,
We are designing a large-scale database application. The current one will
receive information from many inputs constantly.
We expect it to grow in one year to 60GB (on average of 4-5GB/Mo).
The database then (after one year) will have a cleaning procedure that will
delete information and the size of the database will not increase
significantly.
Here are a few questions:
1. What are the guide lines to design and implement such a database? Where
can I find information on the web on such cases?
2. From database creation point of view - should we use a few files that
will create the database or should we use only one ? If we use a few files,
what happends to clustered indexes? Where can I find more reading material?
3. The database has the management tables of the application and the data
tables. One data table will hold most of the information in that database. Do
you think I need to divide te table? if so, how do we do it? What is the
common practice in such cases where a huge table holds so much info
(Currently we have a similar database with 27M records in).
how do you build efficient queries? How do you manage the data in the
separate tables? How do you manage indexes? and again where can I find
material on this?
We know to look inside the BOL but we are looking for common practice
solutions.
TIA!!
Noam
Please don't post independently in separate newsgroups. You can add
multiple newsgroups to the header and then all the answers appear as one.
See my reply in the other newsgroup.
Andrew J. Kelly SQL MVP
"Noam" <Noam@.discussions.microsoft.com> wrote in message
news:2DCD3F8D-DFCF-46F7-BB1C-30355D49B321@.microsoft.com...
> Hi,
> We are designing a large-scale database application. The current one will
> receive information from many inputs constantly.
> We expect it to grow in one year to 60GB (on average of 4-5GB/Mo).
> The database then (after one year) will have a cleaning procedure that
will
> delete information and the size of the database will not increase
> significantly.
> Here are a few questions:
> 1. What are the guide lines to design and implement such a database? Where
> can I find information on the web on such cases?
> 2. From database creation point of view - should we use a few files that
> will create the database or should we use only one ? If we use a few
files,
> what happends to clustered indexes? Where can I find more reading
material?
> 3. The database has the management tables of the application and the data
> tables. One data table will hold most of the information in that database.
Do
> you think I need to divide te table? if so, how do we do it? What is the
> common practice in such cases where a huge table holds so much info
> (Currently we have a similar database with 27M records in).
> how do you build efficient queries? How do you manage the data in the
> separate tables? How do you manage indexes? and again where can I find
> material on this?
> We know to look inside the BOL but we are looking for common practice
> solutions.
> TIA!!
> Noam
>
|||Thank you for your fast reply. This is the first time I posted here and I
will do as you suggest next time!.
Thanks.
Noam
"Andrew J. Kelly" wrote:

> Please don't post independently in separate newsgroups. You can add
> multiple newsgroups to the header and then all the answers appear as one.
> See my reply in the other newsgroup.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Noam" <Noam@.discussions.microsoft.com> wrote in message
> news:2DCD3F8D-DFCF-46F7-BB1C-30355D49B321@.microsoft.com...
> will
> files,
> material?
> Do
>
>

Large scale databases - common practice

Hi,
We are designing a large-scale database application. The current one will
receive information from many inputs constantly.
We expect it to grow in one year to 60GB (on average of 4-5GB/Mo).
The database then (after one year) will have a cleaning procedure that will
delete information and the size of the database will not increase
significantly.
Here are a few questions:
1. What are the guide lines to design and implement such a database? Where
can I find information on the web on such cases?
2. From database creation point of view - should we use a few files that
will create the database or should we use only one ? If we use a few files,
what happends to clustered indexes? Where can I find more reading material?
3. The database has the management tables of the application and the data
tables. One data table will hold most of the information in that database. Do
you think I need to divide te table? if so, how do we do it? What is the
common practice in such cases where a huge table holds so much info
(Currently we have a similar database with 27M records in).
how do you build efficient queries? How do you manage the data in the
separate tables? How do you manage indexes? and again where can I find
material on this?
We know to look inside the BOL but we are looking for common practice
solutions.
TIA!!
NoamPlease don't post independently in separate newsgroups. You can add
multiple newsgroups to the header and then all the answers appear as one.
See my reply in the other newsgroup.
Andrew J. Kelly SQL MVP
"Noam" <Noam@.discussions.microsoft.com> wrote in message
news:2DCD3F8D-DFCF-46F7-BB1C-30355D49B321@.microsoft.com...
> Hi,
> We are designing a large-scale database application. The current one will
> receive information from many inputs constantly.
> We expect it to grow in one year to 60GB (on average of 4-5GB/Mo).
> The database then (after one year) will have a cleaning procedure that
will
> delete information and the size of the database will not increase
> significantly.
> Here are a few questions:
> 1. What are the guide lines to design and implement such a database? Where
> can I find information on the web on such cases?
> 2. From database creation point of view - should we use a few files that
> will create the database or should we use only one ? If we use a few
files,
> what happends to clustered indexes? Where can I find more reading
material?
> 3. The database has the management tables of the application and the data
> tables. One data table will hold most of the information in that database.
Do
> you think I need to divide te table? if so, how do we do it? What is the
> common practice in such cases where a huge table holds so much info
> (Currently we have a similar database with 27M records in).
> how do you build efficient queries? How do you manage the data in the
> separate tables? How do you manage indexes? and again where can I find
> material on this?
> We know to look inside the BOL but we are looking for common practice
> solutions.
> TIA!!
> Noam
>|||Thank you for your fast reply. This is the first time I posted here and I
will do as you suggest next time!.
Thanks.
Noam
"Andrew J. Kelly" wrote:
> Please don't post independently in separate newsgroups. You can add
> multiple newsgroups to the header and then all the answers appear as one.
> See my reply in the other newsgroup.
>
> --
> Andrew J. Kelly SQL MVP
>
> "Noam" <Noam@.discussions.microsoft.com> wrote in message
> news:2DCD3F8D-DFCF-46F7-BB1C-30355D49B321@.microsoft.com...
> > Hi,
> >
> > We are designing a large-scale database application. The current one will
> > receive information from many inputs constantly.
> >
> > We expect it to grow in one year to 60GB (on average of 4-5GB/Mo).
> >
> > The database then (after one year) will have a cleaning procedure that
> will
> > delete information and the size of the database will not increase
> > significantly.
> >
> > Here are a few questions:
> > 1. What are the guide lines to design and implement such a database? Where
> > can I find information on the web on such cases?
> > 2. From database creation point of view - should we use a few files that
> > will create the database or should we use only one ? If we use a few
> files,
> > what happends to clustered indexes? Where can I find more reading
> material?
> > 3. The database has the management tables of the application and the data
> > tables. One data table will hold most of the information in that database.
> Do
> > you think I need to divide te table? if so, how do we do it? What is the
> > common practice in such cases where a huge table holds so much info
> > (Currently we have a similar database with 27M records in).
> > how do you build efficient queries? How do you manage the data in the
> > separate tables? How do you manage indexes? and again where can I find
> > material on this?
> >
> > We know to look inside the BOL but we are looking for common practice
> > solutions.
> >
> > TIA!!
> >
> > Noam
> >
>
>

Large scale changes of data in SQL Server 2005

Hi
We are using a Helpdesk system which uses SQL Server 2005 as the back
end. Our office is the group HQ for all our subsidaries and affiliates,
so we tend to get a lot of IT support calls from different
organisations.
When HD agents log the call, a field exists to identify which
organisation this is, e.g. Company A, Company B and so on.
Company A has decided to change their name to Company Z. This needs to
be reflected in the software not just from this point on, but also
historically, i.e. even a called in 2005 by an employee of Company A
should now read as a call logged by an employee of Company Z.
What is the best method to change this in the database? Luckily,
Company A has been one of the smaller companies, so the total amount of
calls by them that exist is about 40.
Many thanks in advance.
SJ
Hi
I hope you do have Company table where you store the names of the companies
and their ID
UPDATE Company SET [Name]='Company Z' WHERE [Name]='Company B'
If your database design is proper you don't need change anything because
the table is refernced by ID anot by NAME
<smokejo@.googlemail.com> wrote in message
news:1163971948.529460.64020@.f16g2000cwb.googlegro ups.com...
> Hi
> We are using a Helpdesk system which uses SQL Server 2005 as the back
> end. Our office is the group HQ for all our subsidaries and affiliates,
> so we tend to get a lot of IT support calls from different
> organisations.
> When HD agents log the call, a field exists to identify which
> organisation this is, e.g. Company A, Company B and so on.
> Company A has decided to change their name to Company Z. This needs to
> be reflected in the software not just from this point on, but also
> historically, i.e. even a called in 2005 by an employee of Company A
> should now read as a call logged by an employee of Company Z.
> What is the best method to change this in the database? Luckily,
> Company A has been one of the smaller companies, so the total amount of
> calls by them that exist is about 40.
> Many thanks in advance.
> SJ
>
|||Uri Dimant wrote:

> Hi
> I hope you do have Company table where you store the names of the companies
> and their ID
> UPDATE Company SET [Name]='Company Z' WHERE [Name]='Company B'
> If your database design is proper you don't need change anything because
> the table is refernced by ID anot by NAME
>
We have a Company table and within it columns for CompanyID and
CompanyName.
I have a couple of questions though...
i) How is it possible to 'see' what values there are for the Company
Name?
ii) Where do I run the command that you mentioned?
iii) Is it possible to actually see all the data in the database and,
if so, how can I do that? For instance, in MS Access you can view the
database and all the info in it...
Sorry, I'm not really an SQL man, so have no idea!
Thanks so much in advance...
|||> i) How is it possible to 'see' what values there are for the Company
> Name?
SELECT * FROM Table WHERE NOT EXISTS (SELECT * FROM Company C WHERE
C.CompanyID=Table.CompanyID)

> ii) Where do I run the command that you mentioned?
Query Analyzer

> iii) Is it possible to actually see all the data in the database and,
What did you mean?

> if so, how can I do that? For instance, in MS Access you can view the
> database and all the info in it...
Enterprise Manager?
<smokejo@.googlemail.com> wrote in message
news:1164110500.619811.76700@.j44g2000cwa.googlegro ups.com...
> Uri Dimant wrote:
> We have a Company table and within it columns for CompanyID and
> CompanyName.
> I have a couple of questions though...
> i) How is it possible to 'see' what values there are for the Company
> Name?
> ii) Where do I run the command that you mentioned?
> iii) Is it possible to actually see all the data in the database and,
> if so, how can I do that? For instance, in MS Access you can view the
> database and all the info in it...
> Sorry, I'm not really an SQL man, so have no idea!
> Thanks so much in advance...
>

Large scale changes of data in SQL Server 2005

Hi
We are using a Helpdesk system which uses SQL Server 2005 as the back
end. Our office is the group HQ for all our subsidaries and affiliates,
so we tend to get a lot of IT support calls from different
organisations.
When HD agents log the call, a field exists to identify which
organisation this is, e.g. Company A, Company B and so on.
Company A has decided to change their name to Company Z. This needs to
be reflected in the software not just from this point on, but also
historically, i.e. even a called in 2005 by an employee of Company A
should now read as a call logged by an employee of Company Z.
What is the best method to change this in the database? Luckily,
Company A has been one of the smaller companies, so the total amount of
calls by them that exist is about 40.
Many thanks in advance.
SJHi
I hope you do have Company table where you store the names of the companies
and their ID
UPDATE Company SET [Name]='Company Z' WHERE [Name]='Company B'
If your database design is proper you don't need change anything because
the table is refernced by ID anot by NAME
<smokejo@.googlemail.com> wrote in message
news:1163971948.529460.64020@.f16g2000cwb.googlegroups.com...
> Hi
> We are using a Helpdesk system which uses SQL Server 2005 as the back
> end. Our office is the group HQ for all our subsidaries and affiliates,
> so we tend to get a lot of IT support calls from different
> organisations.
> When HD agents log the call, a field exists to identify which
> organisation this is, e.g. Company A, Company B and so on.
> Company A has decided to change their name to Company Z. This needs to
> be reflected in the software not just from this point on, but also
> historically, i.e. even a called in 2005 by an employee of Company A
> should now read as a call logged by an employee of Company Z.
> What is the best method to change this in the database? Luckily,
> Company A has been one of the smaller companies, so the total amount of
> calls by them that exist is about 40.
> Many thanks in advance.
> SJ
>|||Uri Dimant wrote:
> Hi
> I hope you do have Company table where you store the names of the companies
> and their ID
> UPDATE Company SET [Name]='Company Z' WHERE [Name]='Company B'
> If your database design is proper you don't need change anything because
> the table is refernced by ID anot by NAME
>
We have a Company table and within it columns for CompanyID and
CompanyName.
I have a couple of questions though...
i) How is it possible to 'see' what values there are for the Company
Name?
ii) Where do I run the command that you mentioned?
iii) Is it possible to actually see all the data in the database and,
if so, how can I do that? For instance, in MS Access you can view the
database and all the info in it...
Sorry, I'm not really an SQL man, so have no idea!
Thanks so much in advance...|||> i) How is it possible to 'see' what values there are for the Company
> Name?
SELECT * FROM Table WHERE NOT EXISTS (SELECT * FROM Company C WHERE
C.CompanyID=Table.CompanyID)
> ii) Where do I run the command that you mentioned?
Query Analyzer
> iii) Is it possible to actually see all the data in the database and,
What did you mean?
> if so, how can I do that? For instance, in MS Access you can view the
> database and all the info in it...
Enterprise Manager?
<smokejo@.googlemail.com> wrote in message
news:1164110500.619811.76700@.j44g2000cwa.googlegroups.com...
> Uri Dimant wrote:
>> Hi
>> I hope you do have Company table where you store the names of the
>> companies
>> and their ID
>> UPDATE Company SET [Name]='Company Z' WHERE [Name]='Company B'
>> If your database design is proper you don't need change anything because
>> the table is refernced by ID anot by NAME
>>
> We have a Company table and within it columns for CompanyID and
> CompanyName.
> I have a couple of questions though...
> i) How is it possible to 'see' what values there are for the Company
> Name?
> ii) Where do I run the command that you mentioned?
> iii) Is it possible to actually see all the data in the database and,
> if so, how can I do that? For instance, in MS Access you can view the
> database and all the info in it...
> Sorry, I'm not really an SQL man, so have no idea!
> Thanks so much in advance...
>

Large scale changes of data in SQL Server 2005

Hi
We are using a Helpdesk system which uses SQL Server 2005 as the back
end. Our office is the group HQ for all our subsidaries and affiliates,
so we tend to get a lot of IT support calls from different
organisations.
When HD agents log the call, a field exists to identify which
organisation this is, e.g. Company A, Company B and so on.
Company A has decided to change their name to Company Z. This needs to
be reflected in the software not just from this point on, but also
historically, i.e. even a called in 2005 by an employee of Company A
should now read as a call logged by an employee of Company Z.
What is the best method to change this in the database? Luckily,
Company A has been one of the smaller companies, so the total amount of
calls by them that exist is about 40.
Many thanks in advance.
SJHi
I hope you do have Company table where you store the names of the companies
and their ID
UPDATE Company SET [Name]='Company Z' WHERE [Name]='Company B'
If your database design is proper you don't need change anything because
the table is refernced by ID anot by NAME
<smokejo@.googlemail.com> wrote in message
news:1163971948.529460.64020@.f16g2000cwb.googlegroups.com...
> Hi
> We are using a Helpdesk system which uses SQL Server 2005 as the back
> end. Our office is the group HQ for all our subsidaries and affiliates,
> so we tend to get a lot of IT support calls from different
> organisations.
> When HD agents log the call, a field exists to identify which
> organisation this is, e.g. Company A, Company B and so on.
> Company A has decided to change their name to Company Z. This needs to
> be reflected in the software not just from this point on, but also
> historically, i.e. even a called in 2005 by an employee of Company A
> should now read as a call logged by an employee of Company Z.
> What is the best method to change this in the database? Luckily,
> Company A has been one of the smaller companies, so the total amount of
> calls by them that exist is about 40.
> Many thanks in advance.
> SJ
>|||Uri Dimant wrote:

> Hi
> I hope you do have Company table where you store the names of the companie
s
> and their ID
> UPDATE Company SET [Name]='Company Z' WHERE [Name]='Company B'
> If your database design is proper you don't need change anything because
> the table is refernced by ID anot by NAME
>
We have a Company table and within it columns for CompanyID and
CompanyName.
I have a couple of questions though...
i) How is it possible to 'see' what values there are for the Company
Name?
ii) Where do I run the command that you mentioned?
iii) Is it possible to actually see all the data in the database and,
if so, how can I do that? For instance, in MS Access you can view the
database and all the info in it...
Sorry, I'm not really an SQL man, so have no idea!
Thanks so much in advance...|||> i) How is it possible to 'see' what values there are for the Company
> Name?
SELECT * FROM Table WHERE NOT EXISTS (SELECT * FROM Company C WHERE
C.CompanyID=Table.CompanyID)

> ii) Where do I run the command that you mentioned?
Query Analyzer

> iii) Is it possible to actually see all the data in the database and,
What did you mean?

> if so, how can I do that? For instance, in MS Access you can view the
> database and all the info in it...
Enterprise Manager?
<smokejo@.googlemail.com> wrote in message
news:1164110500.619811.76700@.j44g2000cwa.googlegroups.com...
> Uri Dimant wrote:
>
> We have a Company table and within it columns for CompanyID and
> CompanyName.
> I have a couple of questions though...
> i) How is it possible to 'see' what values there are for the Company
> Name?
> ii) Where do I run the command that you mentioned?
> iii) Is it possible to actually see all the data in the database and,
> if so, how can I do that? For instance, in MS Access you can view the
> database and all the info in it...
> Sorry, I'm not really an SQL man, so have no idea!
> Thanks so much in advance...
>

Large report to fit onto 1 page

Hi,

I've browsed the forums and found other posts outlining the same issue and the answer was no..there is no scale to fit option in reporting services.. now a year later i was wondering if anything had been done about this?

Is there anyway to get a 20 column report to fit onto 1 page on printing?

Many thanks

Dave

Have you submitted this suggestion to https://connect.microsoft.com/SQLServer/Feedback ?

If so, let me know the URL and I will also vote on it.

There is nothing in SSRS now that allows "fit to page", but there really should be, especially for the matrix control.

BobP