Thanks for expanding your question.
I agree with jekerekes: FactoryTalk View's relationship with Microsoft SQL Server is in the background: it creates an Instance of the SQL Server for its own use but doesn't really expose it to the user.
The principal connection between FactoryTalk View and an ODBC database (including Microsoft SQL Server) is for data logs: this includes the Data Log Models that fuel the Trend objects, as well as the Alarm and Event logs, and the diagnostic event logs.
For objects that aren't alarms, events, or trends, you can access information inside an external database using VBA and Microsoft ActiveX Data Objects (ADO). This typically requires the execution of a Command to run the VBA routine, so it's run by an Event or a button onscreen, rather than just being "create a display field and connect it to a database field".
I'm not trying to push Ignition on you: I don't have a commercial relationship with Inductive Automation. It's just that "query data from an external SQL database and show it onscreen" is the fundamental feature on which Ignition is built, rather than something you can get to with custom code, and I thought that was important to your original question.