Activity overview
Latest activity by Brian Donahue
I ran into a similar issue where the source code window didn't work last week and the cause of the problem was a corrupt registry key. You may want to try deleting this registry key:
HKEY_CURRENT_USER\Software\Red Gate\ANTS Performance Profiler 5\Dock States\Main Window\DockManagerData\Panels\Item1
/ comments
I ran into a similar issue where the source code window didn't work last week and the cause of the problem was a corrupt registry key. You may want to try deleting this registry key:
HKEY_CURRENT_U...
Hello,
The evidence suggests that ANTS Memory profiler is causing the worker process to crash. There is a named pipe created inside w3wp's process that sends the data into the ANTS Memory Profiler process. Of course the cause of this is unclear. I can send you an email and we can try to work out the root cause of this crash, which may involve getting a crash dump from w3wp.exe. / comments
Hello,
The evidence suggests that ANTS Memory profiler is causing the worker process to crash. There is a named pipe created inside w3wp's process that sends the data into the ANTS Memory Profiler ...
Was this the registry hack to get the Source code window back? This is the only registry hack for ANTS that I did this week. I believe it was deleting HKEY_CURRENT_USER\Software\Red Gate\ANTS Performance Profiler 5\Dock States\Main Window\DockManagerData\Panels\Item1. This doesn't seem to be related to the problem mentioned above, though. / comments
Was this the registry hack to get the Source code window back? This is the only registry hack for ANTS that I did this week. I believe it was deleting HKEY_CURRENT_USER\Software\Red Gate\ANTS Perfo...
Hi,
I'm sorry I don't know what the problem is based on the supplied information. I suppose the relevant questions for me to ask are:
The version of memory profiler
Whether or not you had successfully taken one or more snapshots
How much free memory was available at the time
Can you send me the log file? (Help->show log folder in v5.x)
Thanks for any information you can provide! / comments
Hi,
I'm sorry I don't know what the problem is based on the supplied information. I suppose the relevant questions for me to ask are:
The version of memory profiler
Whether or not you had successf...
Hi,
SQL Compare 8.2 is not currently on the release schedule, so it could be a few months away. / comments
Hi,
SQL Compare 8.2 is not currently on the release schedule, so it could be a few months away.
Hello,
If the method is in bold, then the performance profiler should show the code for that method in the code window if it exists on the disk or is saved inside a previous session's saved results.
This is probably a bad situation that the docking windows can get into from time to time. I'd try the Reset Docking Windows option from the View menu. That shout get all the windows back into their default positions. / comments
Hello,
If the method is in bold, then the performance profiler should show the code for that method in the code window if it exists on the disk or is saved inside a previous session's saved results...
Hello,
SQL Compare is designed to syncrhonize only the two schemas being compared, so it will alter wherever possible unless an object needs to be recreated for technical reasons. There is no option that will cause an "IF EXISTS.." to be scripted, but this feature has been requested pretty frequently and will probably appear in a future version (it's tentatively scheduled for 8.2). / comments
Hello,
SQL Compare is designed to syncrhonize only the two schemas being compared, so it will alter wherever possible unless an object needs to be recreated for technical reasons. There is no optio...
Hi Lindsey,
Usually the opposite is true -- jobs fail without reporting back to the SQL Agent and end up as a success. This is because SQL Backup's extended stored procedure does not raise errors back to the SQL Agent; it sets a return code and a SQL-specific return code.
The bit that is flagging the job as failed appears lower down in the script than the snippet you'd sent. If you look for the RAISERROR command, this is the bit you're interested in.
Normally, you want to flag only error codes greater than 500, otherwise your job will be flagged as an error when mail could not be sent or the SQL Backup Agent had to retry because there was not enough free contiguous VAS memory. For example:
DECLARE @errorcode INT
DECLARE @sqlerrorcode INT
EXECUTE master..sqlbackup '-SQL "BACKUP LOG [database] TO DISK = ''D:\sql2005\MSSQL.1\MSSQL\Backup\<TYPE>_<DATABASE>_<DATETIME YYYYmmddhhnnss>.sqb'' WITH DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COPYTO = ''\\server\Backup'', THREADCOUNT = 2"', @errorcode OUT, @sqlerrorcode OUT;
IF (@errorcode >= 500) OR (@sqlerrorcode <> 0)
BEGIN
RAISERROR ('SQL Backup failed with exit code: %d SQL error code: %d', 16, 1, @errorcode, @sqlerrorcode)
END
/ comments
Hi Lindsey,
Usually the opposite is true -- jobs fail without reporting back to the SQL Agent and end up as a success. This is because SQL Backup's extended stored procedure does not raise errors b...
ANTSApplicationHost: cut-down webserver for IIS 7 users
Hi all,
I have written a tiny web server application for users who are having trouble getting profiler working with IIS. Unfortunately, this only works with IIS 7, so you will need Windows Vista or...
MSI error 1603 when installing over Beta
Hi all,
Just to let you know, there is a known problem with one of the earlier builds of the ANTS Profiler 4.0 Beta where it does not uninstall cleanly and therefore prevents the release version fr...