February 16, 2011 at 10:30 pm
Comments posted to this topic are about the item Visual Studio Tools
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
February 16, 2011 at 10:30 pm
I had no idea on this. Got the answer after googling a bit. 🙂
M&M
February 16, 2011 at 11:35 pm
Thanks for the question.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
February 17, 2011 at 12:54 am
Even I was not having any idea about this. Googled and got the answer.
This was a new learning for me.
Thanks.
February 17, 2011 at 2:00 am
I couldn't even get the answer by googling! Does anyone have a reference?
Thanks,
Duncan
February 17, 2011 at 2:05 am
Please find details on the below url:
http://msdn.microsoft.com/en-us/library/z29kb47d(v=vs.71).aspx
February 17, 2011 at 3:06 am
tejaswini.patil (2/17/2011)
Please find details on the below url:http://msdn.microsoft.com/en-us/library/z29kb47d(v=vs.71).aspx
Thanks for the link. Although it's for Visual Studio .Net 2003, I can browse to the newer versions from there.
February 17, 2011 at 5:45 am
Learnt something new today!! Thanks for the question.
February 17, 2011 at 7:19 am
tejaswini.patil (2/17/2011)
Please find details on the below url:http://msdn.microsoft.com/en-us/library/z29kb47d(v=vs.71).aspx
According to that link:
"A database reference is simply a pointer to a database."
I chose the pointer option and got it wrong. So, is there two correct options?
February 17, 2011 at 7:27 am
The link says
"
Database References
The database project now includes the concept of database reference. A database reference is simply a pointer to a database. Whenever you create a database reference, the database project immediately checks the list of database connections in Server Explorer and if there is no connection to that database, it creates such a connection for you automatically. A database reference differs from a database connection, because a reference is merely a pointer; it does not allow you to enumerate the contents of the database. A database connection, on the other hand, lets you inspect the contents of the database.
A database reference is persisted with the database project. When you save a project to disk, the reference is saved. When another user opens the project and begins using it, the reference is available to that user. Furthermore, when any user opens a database project, the project checks that user's Server Explorer for a corresponding connection and if no such connection exists, the database project automatically creates it. "
i.e. a new concept of Database Reference is introduced which is a pointer to a database.
So answer to the question should be "Database Reference".
February 17, 2011 at 7:28 am
I am sorry for the font size. I selected 7 thinking that it would be smaller.
February 17, 2011 at 7:30 am
Can someone suggest a good reference to learn more about Visual Studio database projects?
Thanks.
February 17, 2011 at 7:30 am
tejaswini.patil (2/17/2011)
I am sorry for the font size. I selected 7 thinking that it would be smaller.
You can still edit your post. Please do. 🙂
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
February 17, 2011 at 7:35 am
Daniel Bowlin (2/17/2011)
Can someone suggest a good reference to learn more about Visual Studio database projects?Thanks.
I blog about it quite a bit here: http://sqlblog.com/blogs/jamie_thomson/archive/tags/Datadude/default.aspx
Its a little bit of a self-promotion but then, I did write the QoD so why not ... 🙂
Otherwise, here is my master list of datadude-related links that I carry everywhere with me:
Datadude stuff
Build and Deploy Databases to an Isolated Development Environment
(http://msdn.microsoft.com/en-us/library/dd193409.aspx)
An Overview of Database Build and Deployment
(http://msdn.microsoft.com/en-us/library/aa833165.aspx)
Apply Test-Driven Development to your Database Projects
(http://msdn.microsoft.com/en-us/magazine/dvdarchive/cc164243.aspx)
Walkthrough: Partition a Database Project by Using Composite Projects
(http://msdn.microsoft.com/en-us/library/dd193415.aspx)
Right sizing the master.dbschema file for better design time performance
Referencing for Shared Server-Level Objects
(http://msdn.microsoft.com/en-us/magazine/dd483214.aspx#id0100036)
Verifying Database Code by Using Unit Tests (MSDN)
(http://msdn.microsoft.com/en-us/library/dd172118.aspx)
Visual Studio 2010 SQL Server Database Projects
(http://msdn.microsoft.com/en-us/library/ff678491.aspx)
A comparison of DAC and regular .dbproj projects
How to: Prepare a Database for Deployment From a Command Prompt by Using VSDBCMD.EXE
(http://msdn.microsoft.com/en-us/library/dd193258.aspx)
------------------------------------------------------------------------------------------------
MSTest stuff
MSTest.exe Command-Line Options
(http://msdn.microsoft.com/en-us/library/ms182489%28v=VS.80%29.aspx)
How to: Run Database Unit Tests from Team Foundation Build
(http://msdn.microsoft.com/en-us/library/aa833210.aspx)
------------------------------------------------------------------------------------------------
Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
February 17, 2011 at 10:00 am
Thanks for the question, I learned something new. 😉
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply