[RESOLVED] Moving from VB6 to VB.NET have some questions about Sql and ADO etc

[jmcilhinney]

Once your app is connection to SQL Server it doesn't care. You can change the connection to connect to a different database or a different server. You can develop your app by attaching an MDF file while debugging and then simply change the connection string when you deploy to connect to an existing database on a local or remote server. It's all the same to your app.

SQL Server will handle a lot of those tasks for you. You should use the in-built capabilities of the server as much as you can. For anything else you can build the functionality into your app when the time comes.

[easymoney]

Been doing some reading, I think the model I am utilmately migrating OLTP type of database.

OLTP Database

Online Transaction Processing (OLTP) relational databases are optimal for managing changing data. They typically have several users who are performing transactions at the same time that change real-time data. Although individual requests by users for data generally reference few rows, many of these requests are being made at the same time.

OLTP databases are designed to let transactional applications write only the data needed to handle a single transaction as quickly as possible. OLTP databases generally do the following:

Support large numbers of concurrent users who are regularly adding and modifying data.

Represent the constantly changing state of an organization, but do not save its history.

Contain lots of data, including extensive data used to verify transactions.

Have complex structures.

Are tuned to be responsive to transaction activity.

Provide the technology infrastructure to support the day-to-day operations of an organization.

Individual transactions are completed quickly and access relatively small amounts of data. OLTP systems are designed and tuned to process hundreds or thousands of transactions being entered at the same time.

The data in OLTP systems is organized primarily to support transactions, such as the following:

Recording an order from a point-of-sale terminal or entered through a Web site.

Placing an order for more supplies when inventory quantities drop to a specified level.

Tracking components as they are assembled into a final product in a manufacturing facility.

Recording employee data.

[easymoney]

I have the Sql Management Studio Express which I can successfully enter Sql statements to Create tables, insert data, etc.

I know I can make an Sql statement to view data from Sql db's like a table displayed in Datagrid, but is there anyway to view the db field names, data types etc. once the DB has already been created?

Here is my example, don't know if it is correct, but it works Sql MSE:

USE master
GO
select * from sysdatabases where name='Northwind'

GO
use "Northwind"

select * from Employees

Also, is there anyway to do this in a visual interface. I guess Sql is a big boy's toy, use Sql statement to do everything... maybe that's why it is Sql. Not having much luck. Thanks.

[easymoney]

Nevermind, I see it now. It is in Sql Management tool to do this....