Comments
Sort by recent activity
Thanks, I look forward to seeing it--would make this tool useful for that team. / comments
Thanks, I look forward to seeing it--would make this tool useful for that team.
Sorry--I was really meaning an "updater" -- not the fresh installer--and thought that's what someone on a thread mentioned they had. / comments
Sorry--I was really meaning an "updater" -- not the fresh installer--and thought that's what someone on a thread mentioned they had.
gflores said:
Am I the only one having issues? It just keeps "indexing" forever and never finishes. I tried this on two computers and different servers. On a different computer, I used an older version and indexing was seconds.
I confirm glfores' issue. Start it up, indexing is fairly quick against my local database. Much slower against remote and Azure. Also seems to reindex every time the server is changed, so switching back and forth is difficult. Then, against a remote server on which I only have permissions for a single database, the "indexing forever" issue begins. Nothing can stop it. Disconnect from the remote server. No change. Disconnect from all servers. No change. Close the Search tab. Reopen. Still "indexing." Have to restart SSMS to get back to ground zero. Since 95% of the time I'm using this against my local development DBs, it's not a showstopper (yet), but it's definitely an issue. As far as accuracy goes--in my initial tests, this release seems to have solved the original problem. / comments
gflores said:
Am I the only one having issues? It just keeps "indexing" forever and never finishes. I tried this on two computers and different servers. On a different computer, I used an old...
Before SQL Search, I used a little proc to search my code...not nearly as slick or in depth, but I've been going to back to it lately--ya'll are welcome to it. (You'll need a tally or numbers table.) CREATE PROCEDURE admin.pFindStringInCode
@StringToFind nvarchar(50)
AS
SET NOCOUNT ON;
SELECT
s.[name] AS SchemaName,
o.[name] AS ObjectName,
CAST(DENSE_RANK() OVER (ORDER BY s.[Name], o.[Name]) AS varchar) + '.' +
CAST(ROW_NUMBER() OVER (PARTITION BY s.[Name], o.[Name] ORDER BY s.[Name], o.[Name]) AS varchar) AS Instance,
'...'+SUBSTRING(m.definition, CHARINDEX(@StringToFind, m.definition, n.Number), 100)+'...' AS Snippet
FROM
sys.sql_modules AS m
JOIN sys.objects AS o ON o.[object_id] = m.[object_id]
JOIN sys.schemas AS s ON o.[schema_id] = s.[schema_id]
CROSS JOIN admin.tbl_Numbers AS n
WHERE
n.Number < LEN(m.definition)
AND SUBSTRING(m.definition, n.Number, LEN(@StringToFind)) = @StringToFind
AND m.definition LIKE N'%'+ @StringToFind + N'%'
SET NOCOUNT OFF;
GO
Nothing much, but it works in a pinch. / comments
Before SQL Search, I used a little proc to search my code...not nearly as slick or in depth, but I've been going to back to it lately--ya'll are welcome to it. (You'll need a tally or numbers table...
Just an update from my side...I sent a PM to Rob with more information on what I see locally. Currently I'm on 3.0.7.1683 and am still getting false positives, and false negatives. If I re-index, it seems to improve...almost to the point of trusting the results again. However I just ran a test using the "exact match" checkbox and it is still not accurate, missing several results which ought to be there even after the reindex. / comments
Just an update from my side...I sent a PM to Rob with more information on what I see locally. Currently I'm on 3.0.7.1683 and am still getting false positives, and false negatives. If I re-index, i...