Random thoughts...
Made in notepad as I was playing with the product...
- In data generation plan, there is no way to "Select All" or "Unselect All". Even support of CTRL-A would be nice.
- Can't copy and paste values out of the Data Generation Preview.
- Changing "Rows to insert" doesn't seem to have any effect on what is in the Data Generation Preview window. Maybe I just didn't play with it enough.
- Can we have an option just to generate Insert scripts rather than doing the inserts behind the scenes for us?
- Error highlighting - I have lots of errors in my Error List relating to my schema objects. (The error is "Unexpected token was encountered" but I'm not worried about that.) It would be nice if, when double-clicking on an error, the resultant script highlights where the error is. Just like dotnet dev.
- "Preview Changes - Rename" dialog. Can you let us resize the top and bottom portions of it by dragging the horizontal bar in the middle.
- Data-->Refactor-->Rename : Can you make that an option when you right-click on an object in the solution explorer
- Allow us to define a naming convention for foreign keys. For example I always use a naming convention of FKTable_PK_Table_XX. It'd be great if the name of that foreign key was constucted AS I type in the relevant details.
- Can we have a GUI for building tables, views, FKs, indexes, etc... otherwise I think you might find that some people would rather use SSMS to create their objects.
- Syntax checker just like in SSMS (CTRL-F5) would be nice.
- I have imported 2 views that I know have valid syntax. VSTS4DB is throwing "Unexpected token was encountered" and both have a CTE defined pretty near to the line/column where it is saying the error is. Did I read somewhere that you don't support SQL2005 yet? That would explain it!!!
Regards
-Jamie
>>8. Allow us to define a naming convention for foreign keys. For example I always use >>a naming convention of FKTable_PK_Table_XX. It'd be great if the name of that >>foreign key was constucted AS I type in the relevant details.
Code snippets (introduced with VS 2005) should be able to address this requirement to some extent, if not completely.
-Tanveer Rashid
These are very valuable comments and suggestions.
To answer some of your questions:
1. In data generation plan, there is no way to "Select All" or "Unselect All". Even support of CTRL-A would be nice.
[Liangxiao] Yes, "Select All" and "Unselect All" will be very useful, and they will be supported in V1 as far as I know.
2. Can't copy and paste values out of the Data Generation Preview.
[Liangxiao] This is a very good suggestion.
3. Changing "Rows to insert" doesn't seem to have any effect on what is in the Data Generation Preview window. Maybe I just didn't play with it enough.
[Liangxiao] Change "Rows to insert" just to change the number of rows you want to insert into your target database during data generation. If you want to change preview row count, you can invoke Tools -> Options main menu, navigate to Database Tools\Data Generator\General settings page, and you can change "Preview row count" there.
4. "Preview Changes - Rename" dialog. Can you let us resize the top and bottom portions of it by dragging the horizontal bar in the middle.
[Liangxiao] We are investigating that.
6. Data-->Refactor-->Rename : Can you make that an option when you right-click on an object in the solution explorer
[Liangxiao] Right now, if you right click the object, you will see a "Rename..." context menu, if you click it, it will also invoke Rename Refactoring.
Hi Jamie,
Thanks for the notes! Please keep them coming, we appreciate your feedback. :)
7. Data-->Refactor-->Rename : Can you make that an option when you right-click on an object in the solution explorer
It actually is. If you right-click a schema object you should see a "Rename..." option.
9. Can we have a GUI for building tables, views, FKs, indexes, etc... otherwise I think you might find that some people would rather use SSMS to create their objects.
Sorry, modeling tools will not be part of this release.
10. Syntax checker just like in SSMS (CTRL-F5) would be nice.
Our T-SQL editor actually provides this. You can access it via the "Validate SQL Syntax" item when you right-click the editor surface (or via Data | T-SQL Editor | Validate SQL Syntax). However, you will notice this is not enabled when viewing the DDL in your database project. These files are parsed on save, so if there are any issues, you will see errors in the Error List.
11. I have imported 2 views that I know have valid syntax. VSTS4DB is throwing "Unexpected token was encountered" and both have a CTE defined pretty near to the line/column where it is saying the error is. Did I read somewhere that you don't support SQL2005 yet? That would explain it!!!
With our CTP3 release our parser does not yet understand all of the SQL 2005 types. However, we should not have any problems with SQL 2000 types. By RTM, our parser will be complete and understand all 2000 and 2005 types.
Thanks!
-Jon
