Getting Started - What to Learn / Tools Advice

Question

Getting Started - What to Learn / Tools Advice

Viewing 3 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

madeley68 Valued Member Points: 71 More actions · Answer 1

Jim,

Thanks for that but with some of the things I need to do, views etc it gets a bit big and messy with Access, I have tried to use it as a front end but there is an issue with Access 2003 and SQL 2005 and its likely the same issue with 2007 / 2008. Nice work if you can get it by MS.

There is a performance issue on queries and I have made a lot of tweaks to JET records etc to minimalise it, but the issues are just going to grow as the db grows. I have another DB which I want to do which will be even bigger so I thought I might aswell learn it now.

The reason I asked about C# was really to build a GUI for it from SQL with just abilities to view / edit data in a datagrid similar to Access but not as complex.

I appreciate the response and thanks for the suggestion.

Regards

Sam

Jeff Moden SSC Guru Points: 1004641 More actions · Answer 2

madeley68 (3/12/2008)
I will do that, strangely I need that on my main table, which has just north of 1.1 Million rows at the minute, I did get a program written for Access but it took forever and I never had a great deal of confidence in it.

Don't forget... Access has indexes as well.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

madeley68 Valued Member Points: 71 More actions · Answer 3

Jeff,

I have indexed and PK columns in the Access DB as I tried to optimise the query performance, other than having indexes I also split the table into years etc to minimise the size. I am aware and use them but why do I get the feeling I am missing something in your post.

I don't think it helps that the same DB is twice the size in 2003 than it is in 97.

I plan to move it after the easter break, but unsure which is the best method. There is the upsizing wizard, which doesn't work with 2008 but works with 2005. I could do bulk imports (CSV or XML) which I would split into years, but I need to get my head around SQL a little bit first, then the dumb questions really start.