Temp database!

Hi everybody!
I'm modelling an application that interacts with a sql database. A db gui handles all the events concerning the database. I'm thinking about having a temp database where I store data before inserting it into the main database. There will be alot of different activities in the database so I don't want to store data straight into the main database during day time.

So my question is if anyone have done something like this before and might confirm if it is a good idea or bad. Is there a known way to deal with this?

User gui -> DB gui -> Temp db - > Main db


thanx alot
Pete

The only real thing you have to keep in mind is to make sure you grant proper permissions on each database. Personally to limit the need to recomplie your GUI thou I would suggest do the logic for all this in stord procedures to make as transparent to the app as possible and easier to alter.

You should always try to limit the access by wrapping processes in Procedures where possible.

Hello!
I've planned to use stored procedures as u say. Have u created something like this? Do u think it´s wise to do it like this?

Pete

Look into Data Transformation Services. Here you can design your own schedules of tasks to perform, such as running SP's, Exe's, scripts and other stuff.
You can then schedule your DTS-package to execute at the time of day you prefer.

Ok, I will certainly look into that. It seems to fit in nicely in my model.

Another issue that I'm thinking about is what programming language I should use to create the application. I'm first a vc++ programmer but I've heard alot of Delphi and that it's quite easy and fast to create apps which mainly contains database events.
Is this something u guys have experience of.

Pete

I used VB.Net myself which i'm in love with. Delphi is "better" in the sense that the compile app doesn't require a bunch off dll's to function. But if you already use vc you probably already have access to VB. Easy to use and easy to connect to db

Ok. I havn't upgraded my Visual Studio to .NET yet unfortunately. So I don't know the advantages of .NET. Would u say that the difference is so great that I could save time using .Net instead. Or is it just minor differences like comforts?

Otherwise I will push my boss to the wall about this.:D

Pete

Oh yeah, VB.Net is as close to pure object oriented as it probably can get (of course not 100% but for VB close enough)

There's a lot of reading to do though, but after a few months you will spit on ever using VB6 =)

VB6 works fine if you're just dabbling a bit and making smaller programs, but for more complex systems I strongly recommend .Net whether it be VB.Net, C# or C++

Only backdraw is that clients running your programs need the .Net framework installed to work (which is free though from MS)

Can't say about Delphi, since I haven't used it in 10 years and I expect it has evolved a lot since then. It probably is worth taking a closer look at. I think it still uses some dialect of Pascal though.

As for me, I'm sticking to VB.Net for the time being.

/Chris

Ok, I just ordered an upgrade to .NET. It's seems stupid to use vb6 when I have the chance to learn .NET.

I just made a test application in VB6 and it's striking how easy it is. And I don't need alot of code to create the db connection. It feels like sheeting compared to vc++.:D

Pete