Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

Dim strCommand2 As String = “DROP TABLE Foo”
Dim cnMyConn As New SqlClient.SqlConnection(strConnect)
‘ “Open” the connection (this is the first time it actually
‘ contacts the database server)
cnMyConn.Open()
‘ Create the command object now
Dim sqlMyCommand As New SqlClient.SqlCommand(strCommand, cnMyConn)
‘ Execute the command
sqlMyCommand.ExecuteNonQuery()
Console.WriteLine(“Table Created”)
Console.WriteLine(“Press enter to continue (you can go check to make sure
that it’s there first)”)
Console.ReadLine()
End Sub
End Module
‘ Change the command
sqlMyCommand.CommandText = strCommand2
sqlMyCommand.ExecuteNonQuery()
Console.WriteLine(“It’s gone”)
Console.WriteLine()
Console.WriteLine(“Press any key to continue...”)
Console.ReadKey()
‘ Clean up
cnMyConn.Close()
A Brief Word on LINQ
Appendix B: Very Simple Connectivity Examples
LINQ is, as I write this, “all the rage” so to speak. For the rare few that haven’t heard of LINQ, it is a
new (or, more accurately, a new attempt at an) access method based on the notion of homogeneous data
sources. LINQ has its own query language — one that is very similar to SQL, and yet different enough to
create no small degree of work when trying to convert between the two.
While LINQ certainly has, and will likely continue for at least a while to have a lot of momentum as the
new way of accessing data, I remain something of a skeptic. Don’t get me wrong. LINQ has some cool
things to offer, but I’ve seen LINQ-type data access notions come and go many times over the years, so
I’ve been trained to question the staying power of such models.
655