FrontEnd

[matrixknow]

Hallo,

I am a newbie and I wonder. Does SQL Server has his own GUI, Forms to input data or is SQL Server just a database on which you plug many different user interfaces, like access or cube or Csharp ?

 

[TamedTech]

Well,

The nearest thing SQLServer has to a GUI is the management studio, but this is really used for administrative tasks, SQL is essentialy designed to be a storage mechanism for other applications, these could built in many different languages, it depends on what you're trying to achieve.

If you tell us a little about the project that you're looking to use SQL for perhaps we can point you in the right direction for developing your front end.

Rob

 

[philhege]

The closest thing SQL has to a GUI is the front-end for SQL Server Reporting Services.

Echoing Rob, let us know what you want to do, your audience, etc. and we can make some suggestions.

Phil Hegedusich
Senior Programmer/Analyst
IIMAK

http://www.iimak.com

-----------
Not NULL-terminated yet.

 

[matrixknow]

Thank You for your answer. For the moment we use an access database as FrontEnd and along linked table we have a BackEnd also in Access. Due to performance trouble with access we like to put our data in Microsoft SQL Server. At that moment SQL Server will functionate as our BackEnd and Access as our FrontEnd. After a while we like to integrate many more things that are for the moment developed in excel and then perhaps it should be easier to migrate every input Forms to SQL Server. I was wondering if SQL Server had its own Forms, like in Oracle there you have Oracle Forms.

 

[belovedcej]

A first step for you then, would be to have all your tables imported into SQL Server (there are wizards for this) and then use linked tables in Access to update those SQL tables. You could keep all the forms you already have created and move the data to a more stable environment.

Once that is done, you may want to research all the options to see if an access front end is what you want long term, but it should be a good patch in the meantime.

 

[SQLSister]

You may not see performance increases using linked tables. You might even see decreases. You will need to re-write the queries as pass-through queries (and preferably as stored procs) using SQL server syntax for better performance. You will not get better performance as long as you are going through the jet engine. Start with your slowest queries and work your way down through them; that's what we did at my old company. Left the ok performing ones in place and only re-wrote the bad ones at first and then worked on the others. In the long run, I'd re-write to a web-based front end and SQL Server back end.

Questions about posting. See faq183-874

 

[belovedcej]

SQLSister,

I concur - I did not represent that accurately.

If the issue is just performance, linked tables are very likely to slow things down further.

I was simply thinking in terms of data integrity. If there is a problem with the database corrupting or there is fear due to the number of users that it will, moving the data to SQLServer and using linked tables will fix that in the short term until a long term solution that also addresses performance is determined.

For myself, I use Access adp files to work with SQL tables and stored procs, which has worked beautifully, but none of my projects have been large scale so the performance issues have simply not been there.