Printable View
I am completely new to SQL Server in general. My company looks to be heading in that direction with the massive growth we are going through. I need to learn SQL Server ASAP. Does anyone know where to go to get the basics on creating databases, and such? Coding is easy as I have some experience in ADO.NET 2.0. I have only connected to access before though, I know nothing on SQL Server.
Thanks in advance!!
Probably your best bet would be to head down to your local book store and pick up a good book. That way you'll always have something to referance.
Is SQL Server like Access? Is there an interface built in like Access that will allow me to manipulate the database and get me familiar with the software?
I have SQL 2005 Express installed from VB2005.
Thanks!
Yes, it's a bit different to access though. If you know access you probably won't have to much trouble switching over, especially if you've got something to reference when you do get stuck.
What is the interface called then? I only see the configuration manager tools in my Start menu.
That's the big difference between ACCESS and MS SQL SERVER.
MS SQL has no interface - it's purely a backend database. There is not "UI" like access for frontend.
Normally one would develop the frontend in VB (well at least most of the people on this VB forum would!).
Is that when the T-SQL language comes in?
Kind of...Quote:
Originally Posted by tacoman667
In ACCESS you really could only write QUERIES (and sub-queries within).
With T-SQL you have IF/blocks and logic flow - similar to a higher level language.
So your queries become almost "query programs".
We've written complete processes in T-SQL STORED PROCEDURES - calculate payrolls, schedule students into high school classes.
All this was done in VB with logic in the past - now in SPROCS with T-SQL - we can do it all on the server...
If I plan to make my own interface in VS2005 which will create databases, tables, and fields within code, will I still need to learn T-SQL or can I do all of that in VB? I want to use SQL because with the amount of data I will be storing and processing, I need something far better then access.
You can write your code using SQL and execute your SQL statements from VB (I believe that is the question).
You might also want to consider wrapping your SQL code in stored procedures, and executing the stored procedures from VB.
If I write all code in SQL, then why would I use VB? Not being confrontational, just wondering. Also, I have read that VS2005 and SQL Server have been integrated ALOT, does this mean that I would not need to learn SQL code and can do it all in VB?
Ifeel like such a n00b. :)
MS SQL server is just a database backend.Quote:
Originally Posted by tacoman667
The ability to wrap queries in STORED PROCEDURES and the ability to have IF/blocks and GOTO and LABEL and LOOPS in those STORED PROCEDURES makes them "little mini-programs".
What's great about that is you now have the backend database have the ability to perform some logic - "calculate this", "archive that" - pretty much whatever you can imagine.
But with all that said, you still get no USER INTERFACE from MS SQL SERVER. That's where the front-end - VB6, VB.NET - even ACCESS - can be used to display data to the user and process user actions.
Yes - the integration is probably stronger with VB.Net and MS SQL then with VB6 and MS SQL, but we still prefer to develop all our SQL (or T-SQL) code outside of the user interface. When you bind a control to the data you hide some of the functionality and thus limit some of your abilities. Yes you can bind controls to tables and whip out simple UI's quickly - but that's just not what we do here.
So basically, if I am understanding you, SQL STORED PROCEDURES are equivilent to a module in VB where you can write all your code. How do those get run if there is no interface to make them run? When you bind to a stored procedure, is it just like binding to a record in a DB through ADO.NET?
Post #2 in this thread:
http://www.vbforums.com/showthread.p...&highlight=gcn
shows how to use VB6/ADO to call a SPROC and how to define the SPROC.
The SPROC definition is really just the CREATE PROCEDURE-through-the-GO statement. The rest is just boilerplate we use to drop/re-create and grant user access to the SPROC.
And another thread:
http://www.vbforums.com/showthread.p...&highlight=gcn
and another...
http://www.vbforums.com/showthread.p...&highlight=gcn
Search the forum for gcn - that's my standard connection string variable - you will find lots of posts. Also search for FUNDSUSER or STUFILESUSER and you will see lots of examples of SPROCS.
Kewlness, thanks for the great info!