Comments
Sort by recent activity
I can confirm that it will sort on alpha order if you click on the 'Name' on the dialog box under 'Objects in Selected Database'. / comments
I can confirm that it will sort on alpha order if you click on the 'Name' on the dialog box under 'Objects in Selected Database'.
Postscript: Customer found that GRANT VIEW DEFINITION was the problem and it now works as expected. / comments
Postscript: Customer found that GRANT VIEW DEFINITION was the problem and it now works as expected.
There is a possibility is that you have insufficient access rights on the database. On SQL Server 2000 you need dbo access, on SQL Server 2005 and 2008, you don’t but you do need some additional permissions.
For anyone out there working with SQL Server on a large or mission critical system it's quite likely that, unless you're the DBA, you're not going to have dbo access to the databases you're working with, particularly if you're working directly with the production servers. Unsurprisingly then we've had a number of complaints from people finding themselves in exactly this situation who want to be able to use SQL Prompt 3, but can't because it generally doesn't work unless you're dbo.
Fortunately my colleague Jon this morning let me know that a solution is at hand for SQL Server 2005 at least, although you're still going to have to be nice to your DBA to make this work (I'd suggest that beer often helps). What you need to do is ask him or her to grant you the VIEW DEFINITION permission on the database of interest. What this means is that you'll be able to see all the meta-data for any object defined in the database, but you won't have access to the objects themselves, so for example you won't be able to read any data from a table unless you have the permissions required to do so.
For example, say your username is "bill" and you need access to the AdventureWorks database, then your DBA would need to execute the following command:
GRANT VIEW DEFINITION ON Database::AdventureWorks TO bill
(Please see our developer's blog post for the full article: http://www.simple-talk.com/community/bl ... 19421.aspx) / comments
There is a possibility is that you have insufficient access rights on the database. On SQL Server 2000 you need dbo access, on SQL Server 2005 and 2008, you don’t but you do need some additional ...
I have submitted this as a problem SP-1222 into our bug database, and will keep you posted. / comments
I have submitted this as a problem SP-1222 into our bug database, and will keep you posted.
I suggest that you go into SSMS file menu, SQL Prompt, through the Prompt cache management, and click Refresh All before importing SQL scripts into SSMS. / comments
I suggest that you go into SSMS file menu, SQL Prompt, through the Prompt cache management, and click Refresh All before importing SQL scripts into SSMS.
You are comparing SQL 2000 and 2005 databases - however sadly in SQL Server 2000 you cannot use a fieldname called 'sysname', so you will have to rename it when comparing between the two versions. / comments
You are comparing SQL 2000 and 2005 databases - however sadly in SQL Server 2000 you cannot use a fieldname called 'sysname', so you will have to rename it when comparing between the two versions.
I'm sorry to say that there isn't a method to pass a pragma or change this part of the scripting at present. However I will pass your request to the developers for assessment for possible inclusion. / comments
I'm sorry to say that there isn't a method to pass a pragma or change this part of the scripting at present. However I will pass your request to the developers for assessment for possible inclusion.
Many thanks for alerting us to this bug - I have entered it in our bug database for review. / comments
Many thanks for alerting us to this bug - I have entered it in our bug database for review.
The best way I think to do this is after you have made your changes to Database A, run a SQL Compare between Database A and an empty database. You will obtain a synchronisation SQL script which you can extract and process - you can run through this script extracting all the lines containing 'sp_addextendedproperty' and insert them to another SQL script (you could write a simple VB application to do this for instance, or use a Perl command). This SQL script in SSMS would then write the extended properties onto Database A for you.
Running SQL Compare then between Database A and Database B would obtain another SQL script that you could process in a similar way, and run that against Database B, and synchronise them.
The alternative would be to write a Toolkit application, extracting and running only the lines containing 'sp_addextendedproperty' / comments
The best way I think to do this is after you have made your changes to Database A, run a SQL Compare between Database A and an empty database. You will obtain a synchronisation SQL script which you...
SQL Compare displays the metrics in the 3. Summary stage in the Synchronization wizard - unfortunately this is not exportable. / comments
SQL Compare displays the metrics in the 3. Summary stage in the Synchronization wizard - unfortunately this is not exportable.