dbTalk Databases Forums  

best practices for writing query log to SQL Server

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss best practices for writing query log to SQL Server in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
FurmanGG
 
Posts: n/a

Default best practices for writing query log to SQL Server - 03-07-2006 , 12:19 PM






I assume the recommended approach for setting up the query log in SSAS2005 is
to write it to a SQL Server database. I have a couple of questions about best
practices...

1. Is msdb the suggested database to put it in?

2. If SQL Server (relational) service isn't started by the time that
analysis services service tries to start, you get an error that it can't
connect to the query log. Is the best practice to make SSAS service dependent
upon the SQL relational service to ensure it's started before SSAS starts?

Reply With Quote
  #2  
Old   
Jéjé
 
Posts: n/a

Default Re: best practices for writing query log to SQL Server - 03-07-2006 , 08:35 PM






i recommand to use a dedicated database for sizing reason.
regarding the volume of log you expect, the database size will growth
quickly and the backup should be created correctly.
so using msdb can provide issues for you other applications (like SSIS);
specially if you have to restore the database!

to add some precedence in the services try to add a key in the registry:
HKLM\system\currentcontrolset\services\MSOLAP
DependOnService (multi string value) = MSSQLSERVER

(search for sample values, or the SQLSERVERAGENT registry key values)


"FurmanGG" <FurmanGG (AT) discussions (DOT) microsoft.com> wrote

Quote:
I assume the recommended approach for setting up the query log in SSAS2005
is
to write it to a SQL Server database. I have a couple of questions about
best
practices...

1. Is msdb the suggested database to put it in?

2. If SQL Server (relational) service isn't started by the time that
analysis services service tries to start, you get an error that it can't
connect to the query log. Is the best practice to make SSAS service
dependent
upon the SQL relational service to ensure it's started before SSAS starts?



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.