Activity overview
Latest activity by jbgreen
Hi Redgate folks.
I can tell you that I still experience this memory-driven crash issue. I have shifted to running SQLSearch only in a separate session on a server with 32GB RAM, and SQLSearch can still crash but much less frequently, and so running it in a separate instance is much better than on my primary hardware. I also have to ensure that I limit the index search to the fewest databases as possible, which reduces the utility of the software. I still feel the tool has some nice capabilities and can be useful as long as users are able to isolate the instance adequately. / comments
Hi Redgate folks.
I can tell you that I still experience this memory-driven crash issue. I have shifted to running SQLSearch only in a separate session on a server with 32GB RAM, and SQLSearch can...
I can report the same memory consumption problem when using SQL Search, using v2.1.0.98. After startup, working set memory on local machine is ~130-160MB, with SQL Search installed as an Add-in.
Connecting to a DB server, opening a SQL Search window, running a search, and then a reindex, and then closing the search window and disconnecting from the server can have working set memory bounce between ~150MB and 1GB. Working set memory can be maintain at any level in between, and can drop down after being stable at a higher level. Memory movement is not predictable. Local machine has 8GB RAM, 64-bit OS. Running Microsoft SQL Server Management Studio 12.0.2000.8 (SQL Server 2014 Mgmt Studio) as 32-bit, so addressable memory is limited to 4GB overall. Excessive memory use of SSMS triggers out of memory condition, as one would expect.
I do not have any other RedGate tools installed.
I like the tool, but this behavior is not acceptable. Please let me know if a solution is available. / comments
I can report the same memory consumption problem when using SQL Search, using v2.1.0.98. After startup, working set memory on local machine is ~130-160MB, with SQL Search installed as an Add-in.
C...