Comments
Sort by recent activity
It's an interesting idea. I can see that keeping long frequently edited scripts as snippets might not be ideal, apart from anything else you can't use prompt whilst editing them! I'll record your asking for some management of templates, and we'll see if there's anything that could be done to help. Access to recently executed queries is something we've heard a few people asking for, and this idea seems like it might partner nicely with that.
Thanks for the feedback
Simon / comments
It's an interesting idea. I can see that keeping long frequently edited scripts as snippets might not be ideal, apart from anything else you can't use prompt whilst editing them! I'll record you...
Thanks for the feedback. Would it be possible to get you to send me the log file ( located in C:\Documents and Settings\<User>\Local Settings\Application Data\Red Gate\SQL Prompt 4\ ) to
simon <dot> jackson <at> red-gate.com so that I can look into the issue further.
It would also be useful to know which version of SSMS and SQL Server you are using, and whether you have, or have had, any other add ins installed in SSMS.
Thanks
Simon / comments
Thanks for the feedback. Would it be possible to get you to send me the log file ( located in C:\Documents and Settings\<User>\Local Settings\Application Data\Red Gate\SQL Prompt 4\ ) to
simon <do...
Oops, sorry. Email to
simon <dot> jackson <at> red-gate <dot> com
Would be excellent. / comments
Oops, sorry. Email to
simon <dot> jackson <at> red-gate <dot> com
Would be excellent.
Would it be possible to send me one of these (in descending order of preference):
- A backup of the database
- A SQL Compare snapshot of the database
- The SQL used to create the schema of the database / comments
Would it be possible to send me one of these (in descending order of preference):
- A backup of the database
- A SQL Compare snapshot of the database
- The SQL used to create the schema of the data...
Ah, the equivalent query for SQL 2000 is
SELECT sysobjects.* FROM sysobjects LEFT JOIN sysusers ON dbo.sysusers.uid = dbo.sysobjects.uid
WHERE sysusers.name is null / comments
Ah, the equivalent query for SQL 2000 is
SELECT sysobjects.* FROM sysobjects LEFT JOIN sysusers ON dbo.sysusers.uid = dbo.sysobjects.uid
WHERE sysusers.name is null
Thanks for the feedback.
It doesn't look like an insufficient memory problem, but rather a problem with cacheing your database.
It would help us solve your problem if you could answer a few questions:
- Which version of SQL Server were you connecting to
- Does this error occur repeatedly, on all databases, or was it just once on one database?
- If the error occurs repeatedly on one database could you run this query against it and post/pm me the results (if any):
SELECT sysobjects.name ,
schemas.name ,
id ,
uid ,
type ,
xtype
FROM sys.sysobjects
LEFT JOIN sys.schemas ON sysobjects.uid = schemas.schema_id
WHERE sys.schemas.name IS NULL
- Is it likely that the database schema changed whilst it was being cached by prompt? / comments
Thanks for the feedback.
It doesn't look like an insufficient memory problem, but rather a problem with cacheing your database.
It would help us solve your problem if you could answer a few questio...
I'm sorry you're having problems with the downgrade process. There may be one more thing to try before reinstalling version 3; there is a repair option. If you find the prompt v3 entry in "Add or Remove Programs" then click "Click here for support information" and hit "Repair", that may fix things.
If not then I would suggest trying the reinstall, and if even that doesn't work I can walk you through some things which should fix the install.
Also, to help me look into fixing this problem for future versions could you give me some more information:
- Which version of v3 did you have installed? [You can find this in support information in add or remove programs]
- Which version of Windows, SSMS/Visual Studio/Query Analyzer are you running?
- Have you had previous versions of SQL Prompt installed?
- Do you have any other add-ins installed for SSMS/Visual Studio?
It would also help if you could have a look in the install directory and see whether Prompt 4 has removed itself.
Many thanks
Simon / comments
I'm sorry you're having problems with the downgrade process. There may be one more thing to try before reinstalling version 3; there is a repair option. If you find the prompt v3 entry in "Add or...
Dirk.
Just thought I should get back to you with some info. The trace flag is currently used as part of the script decryption process. This allows you to see the contents of encrypted stored procedures if you have appropriate permissions. It seems that we failed to learn a lesson from SQL Compare that allowing people to turn this off is a must!
We'll make sure that this option is implemented for the next build we push out.
Simon / comments
Dirk.
Just thought I should get back to you with some info. The trace flag is currently used as part of the script decryption process. This allows you to see the contents of encrypted stored pro...
Oops, looks like we double encoded. If you still wish to try out the v4 EA then you should be able to copy the section from the v3 options file and run it through an html encoder. [ e.g. http://www.barelyfitz.com/projects/encoder/ and select the "HTML entities" option ]
Thanks for the feedback, we'll look at putting an automated alias upgrade alongside the snippet upgrade in the final version.
Hope the rest of the EA is better for you! / comments
Oops, looks like we double encoded. If you still wish to try out the v4 EA then you should be able to copy the section from the v3 options file and run it through an html encoder. [ e.g. http...
The magic characters are things called 'Optional Hypen Character's. They are inserted in order to make Word choose to line break at 'nice' places where neccesary. e.g. "vwDim[break]Currency" rather than "vwD[break]imCurrency".
They should only be visible when you have the 'Display all formatting' option enabled in word. (I think that's what it's called, don't have Word to hand atm.), and not in any printed output. I'm afraid I can't give you any strategy for removing them from the actual document, but I suspect it's possible.
The issue with outline view is one we are aware of, unfortunately we didn't manage to work out a neat solution that allowed us to get the formatting right. I know that open office is able to show the outline correctly if that's any help! Out of interest could you tell us why you were wanting to use the outline view? It's all useful stuff to add to the change request! / comments
The magic characters are things called 'Optional Hypen Character's. They are inserted in order to make Word choose to line break at 'nice' places where neccesary. e.g. "vwDim[break]Currency" rath...