How can we help you today? How can we help you today?
Rick
I had nearly a same problem, like SeanX. I wanted to document the "outer" connections of our database - which form uses which SP-s(?). Today I've installed the newest version of SQL Doc, and it WORKS nearly on that way, which was expected  earlier [image]   --!!!!! Feel free to copy this scripts: !!!! -- Adding own extended properties: -- Stored procedure EXEC sp_addextendedproperty  @name=N'ATHOS_usage', @value=N'Forms: main, syshealth',  @level0type=N'SCHEMA', @level0name=N'dbo',  @level1type'PROCEDURE', @level1name=N'API_ATHOS_warning', GO -- Table EXEC sys.sp_addextendedproperty  @name=N'ATHOS_usage', @value=N'Felhasználói felületen megjelenik' ,  @level0type=N'SCHEMA', @level0name=N'dbo',  @level1type=N'TABLE', @level1name=N'almero' GO -- Column EXEC sys.sp_addextendedproperty  @name=N'ATHOS_usage', @value=N'Upper  connection point identifyer' ,  @level0type=N'SCHEMA', @level0name=N'dbo',  @level1type=N'TABLE', @level1name=N'almero',  @level2type=N'COLUMN', @level2name=N'fomeropont_id' GO Comments: "ATHOS_usage" - optional extended property name, in this case from the SW name (ATHOS) "API_ATHOS_warning" - SP in our database "almero" - DB table  "fomeropont_id" DB field The result (screenshots of SqlDoc): [image] [image] I've only one little wish for Red-Gate folks: any time, in the next version of SqlDoc: - check the database for existing optional extended property names - allow to add - edit - delete on some points of SqlDoc surface this properties In the meantime, I congratulate you on this development, and I can live with the fact that these features I have to edit via Management Studio  [image] Best regards: Richard Dragossy / comments
I had nearly a same problem, like SeanX. I wanted to document the "outer" connections of our database - which form uses which SP-s(?). Today I've installed the newest version of SQL Doc, and it WOR...
0 votes
Hi Paul! Meantime I had some tests with Your Tool [image] on the weekend. Disable some properties; disable SQL Prompt itself /Behavior: Use SQL Prompt disabled/; Uninstall SQL Search and so on. Finally I've read on red-gate.com, then .NET 3.5 or higher needs. Downloaded and installed .NET 4.0 framework on my computer. After some computer reboots :oops: (and reinstalling SQL Search after installing .NET 4.0) - everything seems to be working correctly. My SSMS- "About" says the next information: Microsoft SQL Server Management Studio -> 10.50.1600.1 Microsoft Analysis Services Client Tools -> 10.50.1600.1 Microsoft Data Access Components (MDAC) -> 6.1.7600.16385 Microsoft MSXML -> 3.0 6.0 Microsoft Internet Explorer -> 8.0.7600.16385 Microsoft .NET Framework -> 2.0.50727.4952 Operating System -> 6.1.7600 I suppose, that the reason of this problem whereever around .NET versions, but I'm not sure in it. The interesting from the information above the .NET 2.0!! Maybe SQL2008R2 needs only 2.0 version? I don't know, whether Your installation process checks the .NET version or not? If not, it's possible, that in time of first installation I had only 2.0 version :?, because after istalling 2008R2 immediately came Your tool .... According to Your questions: My simptoms WERE the next: 1. Start SSMS with disabled SQL prompt, working half our - no problems. 2. Enable SQL prompt - SSMS immediately completely hangs - hour-glass - Task Manager - kill.... Now "Find Invalid Objects" works on my local computer without any problems, on client's side (connected via VPN) stops with timeout. 3. I'm working on large databases (over 250 user table, 500 USP 200 VIEW, 2000 constraints ..), I had no experience on small ones. Regards: Richard / comments
Hi Paul! Meantime I had some tests with Your Tool on the weekend. Disable some properties; disable SQL Prompt itself /Behavior: Use SQL Prompt disabled/; Uninstall SQL Search and so on. Finally I...
0 votes