How can we help you today? How can we help you today?
bill.wehnert
1. Dependency graph. A visual representation with a diagram showing all of the entities (color coded by type) that depend on this entity. 2. An Foreign Key graph that shows all related tables. Maybe with an arrow showing which way the dependency is going. 3. I'll also agree that I'd love to see the Diagrams be imported if possible. Don't know if SMO lets you export to an image via the API, but if you could embed that in the help file, that would be huge. I don't care right now if you made the diagram linkable (I click on a table - it takes me to that part of the help) -just having the diagram(s) would be a huge bonus I think. 4. Ability to add other types of data on a table. Basically the ability to create my own Extended properties - maybe define them at a project level and say that they are a Table/Field/Sproc/View/Function/etc property and then the editor would let me fill in the values at the appropriate spot. Even cooler would be to specify the data type and length so that you could have some mask fields available (say for capturing only a date, etc). 5. Ability to store all of the extended properties outside of the database so that if something were to happen and you had to rebuild your docs on a backup or on another server, you'd have all of your information available. This would be helpful too if while you are designing you would rather drop the table and rebuild it to put the fields in the order you want. It's a small thing, but would be helpful to me. / comments
1. Dependency graph. A visual representation with a diagram showing all of the entities (color coded by type) that depend on this entity. 2. An Foreign Key graph that shows all related tables. Ma...
0 votes
Thank Tanya, is there a better description of what this layout functionality provides? Thanks. / comments
Thank Tanya, is there a better description of what this layout functionality provides? Thanks.
0 votes
I had a backup failure with the same error codes the other day and looking at the log it said this: 9/8/2007 12:37:26 AM: Backing up MYDATABASE (full database) on PROD instance to: E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_20070908_003726.sqb 9/8/2007 12:37:26 AM: BACKUP DATABASE [MYDATABASE] TO DISK = 'E:\Backups\MSSQL\MYDATABASE\FULL_PR OD_MYDATABASE_20070908_003726.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', PASSWORD = 'XXXXXX XXXX', KEYSIZE = 256, ERASEFILES_ATSTART = 4, COMPRESSION = 3, THREADS = 1 9/8/2007 12:37:27 AM: Deleting old backup file: E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_2 0070903_002916.sqb 9/8/2007 1:36:23 AM: Thread 0 error: Error 620: Error writing to backup file(s). Process terminated unexpectedly. Error code: -2139684860 Thread 0 warning: Warning 210: Error writing to backup file: E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_20070 908_003726.sqb Warning: System error code: (Insufficient system resources exist to complete the requested service) 9/8/2007 1:36:23 AM: Server: Msg 3013 BACKUP DATABASE is terminating abnormally. 9/8/2007 1:36:23 AM: Server: Msg 3271 A nonrecoverable I/O error occurred on file "SQLBACKUP_1E4CD5EC-5A80-4ECC-961E-870A26F5860D:" 995(The I/O operation has been aborted because of either a thread exit or an application request.). 9/8/2007 1:36:23 AM: Server: Msg 3202 Write on "SQLBACKUP_1E4CD5EC-5A80-4ECC-961E-870A26F5860D" failed: 112(There is not enough space on the disk.) The error claims that I had insufficient disk space. But checking the drive, I had over 199gb of disk space free. The backup worked (at least according to the UI and I see a file there - it's 10gb (compressed/encrypted) and the other backups after it continued without a problem. I didn't look in the directory to see if it had actually deleted the old backup that supposedly failed above that day - so I don't know if it got deleted then or on the next backup cycle. Anyway - thought you would like to know that this happened. Using version 5.1.0.2781. / comments
I had a backup failure with the same error codes the other day and looking at the log it said this: 9/8/2007 12:37:26 AM: Backing up MYDATABASE (full database) on PROD instance to: E:\Backups\MSSQL...
0 votes
I don't have this directory "C:\Program Files\Microsoft SQL Server\80\COM\" anymore. It looks like it went when I uninstalled SQL 2000. Do I need to reinstall SQL 2000 now? I also checked on that key and it's not in my registry. / comments
I don't have this directory "C:\Program Files\Microsoft SQL Server\80\COM\" anymore. It looks like it went when I uninstalled SQL 2000. Do I need to reinstall SQL 2000 now? I also checked on that ...
0 votes