Error Log Analysis Services
Contents |
Christen - MSFTJanuary 2, 20123 0 0 0 Today's blog will cover the types of logs/data that we typically request when investigating Analysis Services issues. Most of these logs (excluding dumps) are analysis services 2000 error log easily readable and you can use them for your own investigation. MS support
Analysis Services Log File
uses a number of tools (mps reports, Support Diagnostic Platform, pssdiag, sqldiag) for automated data collection. Unfortunately these tools are msmdsrv.log location not suitable for SSAS data collection yet. This will hopefully change in the near future. Until then we are stuck with manual or semi-automated data collection. The kind of data we need
Sql Server Analysis Services Error Log
to analyze will obviously depend on the nature of the problemunder investigation. In the next section I list data that will be required for almost every problem analysis. General data:
1. msmdsrv.ini The configuration file for the SSAS instance "msmdsrv.ini" can be found in the "\config" folder of the SSAS instance. Typically something like "C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config". If you are unsure about the ssas logging cube processing location, then have a look at the properties of the SSAS service under "services.msc". The "path to executable" field will have the config file folder as "-s" startup parameter: f.i. "C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\bin\msmdsrv.exe" -s "C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config" "msmdsrv.ini"contains the server properties in XML format. You should not edit it unless MS support asks you to do so. And even then do it very carefully. The supported interface for changinginstance properties is SQL Server Management Studio. 2. windows event logs I guess I won't have to tell you much about windows event logs. They have been around forever and you can access them via "Administrative Tools" -> "Event Viewer". SSAS error messages will appear in the application log. System problems (memory, disk space) will appear in system log. Forproblem analysis weare interested in both, system + application event log. Please savethem in.txt or .csv format in order to ensure that event resolution happens on the source server. 3. system information / msinfo32 This log gives us valuable information about your host machine setup. The number + type of CPUs, RAM size, page file size and lots of other hardware related information. Please save as systehere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn
Ssas Query Log
more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags
Msmdsrv.log, Type: 3, Category: 256, Event Id: 0xc1000016
Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, ssas log user activity helping each other. Join them; it only takes a minute: Sign up Error Log records in SSAS up vote 3 down vote favorite 1 We are processing cubes every day in job activity monitor, But on weekends https://blogs.msdn.microsoft.com/as_emea/2012/01/02/data-collection-for-troubleshooting-analysis-services-issues/ w are receving email notification like "cube processing hase been failed". Is there any way to maintain error logs (like in ssis) on cubes? sql-server error-handling ssas share|improve this question asked Oct 22 '12 at 8:44 Sandeep Pulikonda 1992521 add a comment| 2 Answers 2 active oldest votes up vote 5 down vote accepted The key mechanisms for maintaining error logs for Analysis Services are to either: Keep track of the data stored in the msmdsrv.log. http://stackoverflow.com/questions/13007737/error-log-records-in-ssas It will be necessary to copy the log off before it gets overwritten. If you are using Analysis Services 2005, 2008, or 2008 R2, you can generate your own trace events as noted in the System-wide Trace file section of the post Analysis Services Processing Best Practces at: http://technet.microsoft.com/en-us/library/cc966525.aspx#EBAA If you are using SQL Server 2012, you can use the XEvents feature as noted in the SSAS documentation Use SQL Server Extended Events (XEvents) to Monitor Analysis Services at: http://msdn.microsoft.com/en-us/library/gg492139.aspx Another approach is to use the SQL Server Profiler runnning in the background so that way you can record all events. But this would be similar to the #2 option. Also note that the #3 option (using XEvents) has the least impact on your Analysis Services server in terms of resource utilization. share|improve this answer answered Nov 5 '12 at 0:03 Denny Lee 50628 add a comment| up vote 0 down vote According to the documentation, logging is configured through a number of server properties that define logging behaviour and locations. share|improve this answer answered Oct 22 '12 at 15:57 Pondlife 12.6k52242 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By postin
File 14 Jan HOW TO: Recycle the SQL Server Analysis Services msmdsrv.log File Posted at 15:39h in MSSQL, SQL MVP, SQLServerPedia Wiki by Thomas LaRock 5 Comments ShareI found this question over at DBA StackExchange http://thomaslarock.com/2015/01/how-to-recycle-the-sql-server-analysis-services-msmdsrv-log-file/ the other day and it left me shaking my head. How is it possible that there is no way to automatically recycle, or reset, the SQL Server Analysis Services (SSAS) error https://books.google.com/books?id=V0JJoPPfR0EC&pg=PT534&lpg=PT534&dq=error+log+analysis+services&source=bl&ots=ckElwgsXAO&sig=5q1Sl7z3GkRfUu716bn8bDZIYRI&hl=en&sa=X&ved=0ahUKEwimuKK83M7PAhWF1x4KHTWEBCsQ6AEIXzAJ log in a similar manner to SQL Server? After all, it's not like the technology doesn't exist to solve this. More than likely it's just not a feature that anyone analysis services asked for, or anyone ever thought would be useful.Until, that is, a log files grows out of control. I know that's certainly happened to me before.Where others see challenge, I see opportunity. I looked at this question as just that, an opportunity to get my hands on SSAS again as well as brush up on some Powershell.The idea was simple enough. First, update error log analysis the SSAS instance with a new filename. Then, restart the instance so that the new log file is used. You can see this in the server properties for SSAS:You will want to enable the advanced properties checkbox (at the bottom) and then find the ‘Log\File' property. You will notice that the column named ‘Restart' has a value of ‘yes' for this setting. If I make a change here and click OK I will be told that my changes require a restart. I could also choose to script this out in which case an XLMA script will appear in a new window. And for a brief moment I thought that I might want to generate an XMLA script and use Powershell to just invoke that script each time, but then I regained my senses and knew that Powershell was better than that.I stumbled a bit putting together my script so I decided to ask Laerte Junior (blog | @LaerteSQLDBA) for some help. He got me back on track and this is what I have now. You can download the script here but befor
from GoogleSign inHidden fieldsBooksbooks.google.com - As the foundation of the Microsoft Business Intelligence Strategy, Microsoft SQL Server 2008 Analysis Services provides users with faster access to data and even more tools for managing and analyzing data across multidimensional objects (databases, dimensions, cubes). Microsoft SQL Server 2008 Analysis...https://books.google.com/books/about/Microsoft_SQL_Server_2008_Analysis_Servi.html?id=V0JJoPPfR0EC&utm_source=gb-gplus-shareMicrosoft SQL Server 2008 Analysis Services UnleashedMy libraryHelpAdvanced Book SearchBuy eBook - $37.67Get this book in printAmazon.comBarnes&Noble.comBooks-A-MillionIndieBoundFind in a libraryAll sellers»Microsoft SQL Server 2008 Analysis Services UnleashedIrina Gorbach, Alexander Berger, Edward MelomedPearson Education, Dec 14, 2008 - Computers - 888 pages 0 Reviewshttps://books.google.com/books/about/Microsoft_SQL_Server_2008_Analysis_Servi.html?id=V0JJoPPfR0ECAs the foundation of the Microsoft Business Intelligence Strategy, Microsoft SQL Server 2008 Analysis Services provides users with faster access to data and even more tools for managing and analyzing data across multidimensional objects (databases, dimensions, cubes). Microsoft SQL Server 2008 Analysis Services Unleashed is the ultimate guide for anyone who is planning to use the latest version of Analysis Services. It gives readers insight into the way Analysis Services functions, and explains practical methods for designing and creating multidimensional objects. It also provides valuable insight into the reasons behind the design decisions taken by the product development team. The authors have been involved with Analysis Services from its earliest days. They have documented in detail the internal features of Analysis Services 2008, explaining server architecture, main data structures, data processing, and query resolution algorithms. Discover the new functionality introduced in Analysis Services 2008 including MDX enhancements and new DMV (dynamic memory views) Work with the Business Intelligence Development Studio, the new Dimension Editor, and Aggregation Designer interfaces Enjoy complete coverage of new Shared Scalable Databases scale-out infrastructure Learn the key concepts of multidimensional modeling Explore the multidimensional object model and its definition language Integrate multidimensional and relational databases Build client applications to access data in Analysis Services U