Click here to monitor SSC

Bart

Software Engineer - Red Gate Software

SmartAssembly Support: How to change the error report maps folder

Published Wednesday, June 09, 2010 6:40 PM

If you've set up SmartAssembly to store error reports in a SQL Server database, you'll also have specified a folder for the map files that are used to de-obfuscate error reports (see Figure 1). Whilst you can change the database easily enough you can't change the map folder path via the UI - if you click on it, it'll just open the folder in Explorer - but never fear, you can change it manually and fortunately it's not that difficult. (If you want to get to these settings click the Tools > Options link on the left-hand side of the SmartAssembly main window.)

 

Error reports database settings in SmartAssembly.

Figure 1. Error reports database settings in SmartAssembly.

The folder path is actually stored in the database, so you just need to open up SQL Server Management Studio, connect to the SQL Server where your error reports database is stored, then open a new query on the SmartAssembly database by right-clicking on it in the Object Explorer, then clicking New Query (see figure 2).

 

 Opening a new query against the SmartAssembly error reports database in SQL Server.

Figure 2. Opening a new query against the SmartAssembly error reports database in SQL Server.

Now execute the following SQL query in the new query window:

SELECT * FROM dbo.Information

You should find that you get a result set rather like that shown in figure 3. You can see that the map folder path is stored in the MapFolderNetworkPath column.

 

Contents of the dbo.Information table, showing the map folder path I set in SmartAssembly.

Figure 3. Contents of the dbo.Information table, showing the map folder path I set in SmartAssembly.

All I need to do to change this is execute the following SQL:

UPDATE dbo.Information
SET MapFolderNetworkPath = '\\UNCPATHTONEWFOLDER'
WHERE MapFolderNetworkPath = '\\dev-ltbart\SAMaps'

This will change the map folder path to whatever I supply in the SET clause.

Once you've done this, you can verify the change by executing the following again:

SELECT * FROM dbo.Information

You should find the result set contains the new path you've set.

Comments

No Comments
You need to sign in to comment on this blog

About Bart Read

Bart has done many things since he started work at Red Gate Software Ltd in August 2004, but nowadays he's (mainly) the product manager for the .NET Developer Tools. He still feels like this is a bit like admitting you were cheering for the Empire whilst watching Star Wars, but for now he's along for the ride. In a previous incarnation he was a project manager leading the .NET Reflector Pro, ANTS Memory Profiler 5, ANTS Performance Profiler 4 & 5, and SQL Prompt 3.0 - 3.6 projects. He still occasionally writes some code and, in the past, has touched the code for most of the Red Gate SQL developer tools... some of them still haven't recovered from the shock. He was born and grew up in Dorset, was educated in Nottingham and London, and likes music and real ale. His photo is extremely misleading.
<June 2010>
SuMoTuWeThFrSa
303112345
6789101112
13141516171819
20212223242526
27282930123
45678910
Automated Script-generation with Powershell and SMO
 In the first of a series of articles on automating the process of building, modifying and copying SQL... Read more...

Converting String Data to XML and XML to String Data
 We all appreciate that, in general, XML documents or fragments are held in strings as text markup. In... Read more...

Geek of the Week: Don Syme
 With the arrival of F# 3.0 Microsoft announced a wide range of improvements such as type providers that... Read more...

How to Document and Configure SQL Server Instance Settings
 Occasionally, when you install identical databases on two different SQL Server instances, they will... Read more...

What's the Point of Using VARCHAR(n) Anymore?
 The arrival of the (MAX) data types in SQL Server 2005 were one of the most popular feature for the... Read more...