Comments
Sort by recent activity
In one similar case, it seems that it was down to one of the database roles being corrupt.
Dropping and recreating the role fixed the issue.
Can you check this out please? / comments
In one similar case, it seems that it was down to one of the database roles being corrupt.
Dropping and recreating the role fixed the issue.
Can you check this out please?
Hi, thanks for the error report. I think that what could be happening is that there is not enough free contiguous memory available to use as buffer space for SQL Backup. This memory exists in SQL Server's MemToLeave area and is a fixed amount (128MB by default).
SQL Backup requires 6*MAXTRANSFERSIZE per thread, so reducing the number of threads or lowering the MAXTRANSFERSIZE value in the script may help. You may use the MAXTRANSFERSIZE keyword in the backup command. The value must be in 64KB multiples (65536) for instance, MAXTRANSFERSIZE=524288. Here is an article describing the SQL Server memory issue in more detail: http://www.red-gate.com/supportcenter/C ... 000142.htm
Hope this helps! / comments
Hi, thanks for the error report. I think that what could be happening is that there is not enough free contiguous memory available to use as buffer space for SQL Backup. This memory exists in SQL S...
We have a solution to the pdb file problem:
1. Register the dll with gacutil (gacutil -i <name.dll>) (remove the existing one from GAC first if necessary)
2. Find the registered dll in GAC and copy manually the pdb file there to the same directory (for example, one of my files ended up here: C:\WINDOWS\assembly\GAC_MSIL\XlMortgageCalc\1.0.0.0__36608c460dc74a10)
Then the source files should be visible in performance profiler.
A colleague and I have tried to prove that it works (on Win 2003 x86, at least). Hope this helps! / comments
We have a solution to the pdb file problem:
1. Register the dll with gacutil (gacutil -i <name.dll>) (remove the existing one from GAC first if necessary)
2. Find the registered dll in GAC and copy...
I'm having the same problem - and I work in support [image]
See if this tactic works for you; http://www.red-gate.com/supportcenter/C ... 000270.htm
make sure the files have read permission for the account that the app pool is running under (NETWORK SERVICE) by default. / comments
I'm having the same problem - and I work in support
See if this tactic works for you;http://www.red-gate.com/supportcenter/C ... 000270.htm
make sure the files have read permission for the account...
Can I just check if you have selected "Wall Clock" timings or "CPU timings" (default). There's a drop down list on the results page (on the right). When profiling using "Wall Clock" timings you usually see transitions dominating. Have you been using the interactive timeline too? Using this, you can select data from only the code path you are really interested in- this helps to filter out "noise" often. / comments
Can I just check if you have selected "Wall Clock" timings or "CPU timings" (default). There's a drop down list on the results page (on the right). When profiling using "Wall Clock" timings you usu...
Its probably best to use the support channel now, yes- the call reference is F25572. / comments
Its probably best to use the support channel now, yes- the call reference is F25572.
I have to be honest- the signs of a "quick fix" are not looking great. I will try my best to get a "private build" out for you as this will be the quickest way of any. Please bear with me.... / comments
I have to be honest- the signs of a "quick fix" are not looking great. I will try my best to get a "private build" out for you as this will be the quickest way of any. Please bear with me....
Looks like we’re storing the number of users as a smallint and it’s not big enough for this. We'll have to log a bug and fix it in later version. (but I'll see if we can get a quick fix out...) / comments
Looks like we’re storing the number of users as a smallint and it’s not big enough for this. We'll have to log a bug and fix it in later version. (but I'll see if we can get a quick fix out...)
The bug reference for this is:
SC-4529 / comments
The bug reference for this is:
SC-4529
Hi, thanks for the report - it looks like you've found something before anyone else. You're explanation sounds credible too. To get to the log file, click in the very, very top left, on the program icon where you have the option to open the log file. You also have the option there to set logging to verbose level which I recommend. Meanwhile I will verify with the product management team as to whether this is a bug (or a feature ;-). / comments
Hi, thanks for the report - it looks like you've found something before anyone else. You're explanation sounds credible too. To get to the log file, click in the very, very top left, on the program...