Comments
Sort by recent activity
Thanks for your reply.
When you say you deliberately set ANSI when scripting the database, which actual 'type' did you select in SQL Compare?
If you are referring to setting ASCII as the type, then any characters that are not part of the ASCII character set will be shown as '?' in the scripts.
If you open the ASCII SQL Compare script in notepad, you will see that the actual file contains the '?'. So SQL compare is comparing a ‘£â€™ to a ‘?’ as an ASCII file cannot contain a £.
Notepad and SSMS can show the characters because they can display Unicode characters, but if you write the file as ASCII it can only write ASCII characters. / comments
Thanks for your reply.
When you say you deliberately set ANSI when scripting the database, which actual 'type' did you select in SQL Compare?
If you are referring to setting ASCII as the type, then...
Thanks for your post.
If a character (£ for example) is not in the character set for the encoding standard, then it will be represented with something like a ? or a square.
When you created the script folder using SQL Compare, what 'Script Encoding Type' did you set in 'Script creation options'? The £ symbol will be shown as a '?' if you use ASCII, but other types like unicode or UTF8 should represent the character correctly. As far as I'm aware UTF8 is backwards compatiable with ASCII and can represent all unicode characters.
I hope this is helpful. / comments
Thanks for your post.
If a character (£ for example) is not in the character set for the encoding standard, then it will be represented with something like a ? or a square.
When you created the scr...
Thanks for your post.
SQL Data Compare supports SQL Backup and native MTF backups as data sources for a comparison.
I don't know a lot about Tivoli, but they probably have a utility that will allow you to convert their backup files to native SQL MTF files.
Once they are in MTF format, you will be able to compare them with SQL Data compare.
I hope this helps. / comments
Thanks for your post.
SQL Data Compare supports SQL Backup and native MTF backups as data sources for a comparison.
I don't know a lot about Tivoli, but they probably have a utility that will allow...
Thanks for your post.
You should be able to do this if you set a WHERE clause on the Detail table.
You can configure this on the 'Tables & Views' tab.
Something like:
where detail_ID in (select unique_Field from Envelope)
I hope this helps. / comments
Thanks for your post.
You should be able to do this if you set a WHERE clause on the Detail table.
You can configure this on the 'Tables & Views' tab.
Something like:
where detail_ID in (select uni...
Thanks for your post.
Have you tried looking at the 'Method Grid' view? This can be found be selecting the 'Show Methods Grid' button at the bottom of the results pane.
If you turn off all the filters such as 'hide insignificant methods' you should see all the methods.
I hope this helps. / comments
Thanks for your post.
Have you tried looking at the 'Method Grid' view? This can be found be selecting the 'Show Methods Grid' button at the bottom of the results pane.
If you turn off all the filt...
Thanks for your reply.
We don't have a system that allows users to check the status of open issues online, so you will need to contact us if you want to find out. / comments
Thanks for your reply.
We don't have a system that allows users to check the status of open issues online, so you will need to contact us if you want to find out.
Thanks for your post.
This feature is on the wishlist list, but it didn't make the first release of SQL Prompt v4.
It should appear in a v4 point release, but I'm not sure exactly when you can expect it.
For your reference the feature tracking code is SP-1329. / comments
Thanks for your post.
This feature is on the wishlist list, but it didn't make the first release of SQL Prompt v4.
It should appear in a v4 point release, but I'm not sure exactly when you can expe...
Thanks for your post.
The message seems to indicate a problem reading an assembly for whatever reason.
This is a pretty vague answer, so hopefully there will be more information in the log file. You can find the logs in Help > Open Log folder
We have seent his kind of thing with AJAX before. The AjaxControlToolkit.dll emits code using reflection and this interferes with dynamic code being emitted by ANTS Profiler at the same time. We have a workaround and that is to go into your bin folder for the web application and delete AjaxControlToolkit.pdb, which will stop ANTS Profiler from attempting to get line-level timings and source code for that dll. The rest of the source code view shouldn't be affected.
The other alternative would be to use method-level only timings, but that would be undesirable if line-level is of interest to you.
I know you're probably not using AJAx, but i thought this information might be useful, in case your issue turns out to be similar. / comments
Thanks for your post.
The message seems to indicate a problem reading an assembly for whatever reason.
This is a pretty vague answer, so hopefully there will be more information in the log file. Yo...
Thanks for your post.
Can I ask which version of SQL Backup 6 you were using when you had this problem?
The reason I ask is because when I create a failing log shipping job, the retry button opens the wizard again, and it is not possible to change focus back to the UI as the wizard is modal.
The only place I could find to change the database names was the first step of the wizard. / comments
Thanks for your post.
Can I ask which version of SQL Backup 6 you were using when you had this problem?
The reason I ask is because when I create a failing log shipping job, the retry button opens ...
Thanks for your reply.
I've managed to reproduce this now based on your last post. It seems that if you select another database in the server explorer before you click retry, it will change the source database in the log shiping setup to be the one selected in the server explorer. It doesn't look like the target database is affected.
I have logged this as a bug with SQL Backup; the bug tracking code is SB-4372.
Hopefully this will be fixed in a future version.
Thanks for taking the time to report this. / comments
Thanks for your reply.
I've managed to reproduce this now based on your last post. It seems that if you select another database in the server explorer before you click retry, it will change the sou...