Databases. SQL, .NET with VB 2k5 xpressss

OOk, here we go...

I need to make a program, that handles a database.
The database needs to be in SQL and i also need to use dot.NET

I chose to use VB to make the program, and so far i have made a basic database using Access as the database handler.

Now im starting on trying to learn SQL, and while there are SO many resources out there to teach me how to control SQL, theres nothing that shows me how to build a front end for the database, and build a program so that a person can create/delete/modify databases, and all the tables and data in the databases themselves.

Im a little bit lost, i dont exactly feel out of my depth, because i know i can work this out, i just need some guidance!

Any help?

"Now im starting on trying to learn SQL, and while there are SO many resources out there to teach me how to control SQL, theres nothing that shows me how to build a front end for the database, and build a program so that a person can create/delete/modify databases, and all the tables and data in the databases themselves."

Access and SQL Server are two TOTALLY DIFFERENT PLATFORMS. Access is great for a "power user", someone one needs a departmental sized database and they need it up and running quickly. Access is also a great tool to begin learning about database, but Access is not SQL or vice-versa...

My perception of your above statements is that you are looking for the "forms builder" component of SQL Server like Access has...sorry my friend no such functionality exists, atleast not right now. Not built into the database product, probably the closest thing would be reporting services and that is for reporting purposes, though I have seen RS wizards use it like a "forms builder" UI to SQL Server lol...

You build a client "forms" front-end to sql server with a variety of tools, but the most common are .Net, pre .Net VB/C++, and pre.Net ASP. You first need to decide if you want your application to be web-based on client/WinForm-based? from there you need to pick a dev tool that supports the application type you wish to create and then get going with it. You connect to SQL Server from these other platforms via a variety of Database Drivers, ADO, ADO.Net, OLEDB, ODBC, etc.

HTH,

Derek

|||did this address your questions? if so please mark an answer.

Databases. SQL, .NET with VB 2k5 xpressss

OOk, here we go...

I need to make a program, that handles a database.
The database needs to be in SQL and i also need to use dot.NET

I chose to use VB to make the program, and so far i have made a basic database using Access as the database handler.

Now im starting on trying to learn SQL, and while there are SO many resources out there to teach me how to control SQL, theres nothing that shows me how to build a front end for the database, and build a program so that a person can create/delete/modify databases, and all the tables and data in the databases themselves.

Im a little bit lost, i dont exactly feel out of my depth, because i know i can work this out, i just need some guidance!

Any help?

"Now im starting on trying to learn SQL, and while there are SO many resources out there to teach me how to control SQL, theres nothing that shows me how to build a front end for the database, and build a program so that a person can create/delete/modify databases, and all the tables and data in the databases themselves."

Access and SQL Server are two TOTALLY DIFFERENT PLATFORMS. Access is great for a "power user", someone one needs a departmental sized database and they need it up and running quickly. Access is also a great tool to begin learning about database, but Access is not SQL or vice-versa...

My perception of your above statements is that you are looking for the "forms builder" component of SQL Server like Access has...sorry my friend no such functionality exists, atleast not right now. Not built into the database product, probably the closest thing would be reporting services and that is for reporting purposes, though I have seen RS wizards use it like a "forms builder" UI to SQL Server lol...

You build a client "forms" front-end to sql server with a variety of tools, but the most common are .Net, pre .Net VB/C++, and pre.Net ASP. You first need to decide if you want your application to be web-based on client/WinForm-based? from there you need to pick a dev tool that supports the application type you wish to create and then get going with it. You connect to SQL Server from these other platforms via a variety of Database Drivers, ADO, ADO.Net, OLEDB, ODBC, etc.

HTH,

Derek

|||did this address your questions? if so please mark an answer.

Database with Many Tables for different applications

Hello,
I work for a company that chose to implement one database with LOTS (126) of tables. There are many applications that use different tables in this database and the users are spread throughout the business areas of the company. The idea for one database w
ith ALL the tables the company uses was for ease of backup (only having to backup 1 database instead of the 20 or so for each applcation).
We do not use stored procedures or relationships on SQL server - just primary keys and handle everything else in the application.
My question is this: Does this sort of setup impede performance of the applications or SQL database? If many users are hitting a set of tables in the database - does this interfere with other users in the same database but using different tables?
Any insight would be appreciated on this topic. Implementers of this model are of the mainframe mindset and I would like validation to its effectiveness.
Thank you for your time,
Angela
http://www.sqljunkies.com/Article/7F...8946C8D0C.scuk for information on common symptoms and tools to assess the performance.
HTH
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Angela" wrote:

> Hello,
> I work for a company that chose to implement one database with LOTS (126) of tables. There are many applications that use different tables in this database and the users are spread throughout the business areas of the company. The idea for one database
with ALL the tables the company uses was for ease of backup (only having to backup 1 database instead of the 20 or so for each applcation).
> We do not use stored procedures or relationships on SQL server - just primary keys and handle everything else in the application.
> My question is this: Does this sort of setup impede performance of the applications or SQL database? If many users are hitting a set of tables in the database - does this interfere with other users in the same database but using different tables?
> Any insight would be appreciated on this topic. Implementers of this model are of the mainframe mindset and I would like validation to its effectiveness.
> Thank you for your time,
> Angela

Database with Many Tables for different applications

Hello,
I work for a company that chose to implement one database with LOTS (126) of
tables. There are many applications that use different tables in this datab
ase and the users are spread throughout the business areas of the company.
The idea for one database w
ith ALL the tables the company uses was for ease of backup (only having to b
ackup 1 database instead of the 20 or so for each applcation).
We do not use stored procedures or relationships on SQL server - just primar
y keys and handle everything else in the application.
My question is this: Does this sort of setup impede performance of the appl
ications or SQL database? If many users are hitting a set of tables in the
database - does this interfere with other users in the same database but usi
ng different tables?
Any insight would be appreciated on this topic. Implementers of this model
are of the mainframe mindset and I would like validation to its effectivenes
s.
Thank you for your time,
Angelahttp://www.sqljunkies.com/Article/7...E8946C8D0C.scuk
for information on common symptoms and tools to assess the performance.
HTH
--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Perform
ance topic.
"Angela" wrote:

> Hello,
> I work for a company that chose to implement one database with LOTS (126) of table
s. There are many applications that use different tables in this database and the us
ers are spread throughout the business areas of the company. The idea for one datab
ase
with ALL the tables the company uses was for ease of backup (only having to backup 1 databas
e instead of the 20 or so for each applcation).
> We do not use stored procedures or relationships on SQL server - just prim
ary keys and handle everything else in the application.
> My question is this: Does this sort of setup impede performance of the ap
plications or SQL database? If many users are hitting a set of tables in th
e database - does this interfere with other users in the same database but u
sing different tables?
> Any insight would be appreciated on this topic. Implementers of this mode
l are of the mainframe mindset and I would like validation to its effectiven
ess.
> Thank you for your time,
> Angela