What I don't know about SQL!

Andy100 · 18-01-2007, 06:45

Is just about everything

and now I need to know it.

Anyone have any good pointers on learning about SQL databases and how to query them?

I'm the financial controller and we've moved our accounting package to a funky new SQL based one.

There have been problems with the transfer and now it's costing us an arseload to call in the consultants to come in and, from what I've seen, do some pretty simple lookups.

At the moment I'm a complete n00b but with your help! I know I can be a master within the week.

Garp · 18-01-2007, 14:18

Umm....

Have you any experience of Microsoft Access?

Strange question I'm sure, but when teaching someone SQL queries I've found it quite handy as I can get them to start with the query gui and then show them the SQL view of the query and explain through it.

There is a pretty good tutorial here:
http://www.w3schools.com/sql/sql_intro.asp

Jonny69 · 18-01-2007, 17:59

A gentle introduction to SQL: http://sqlzoo.net/

I found that quite useful for the basics. You learn quite quickly when you're working with it though.

What's the accounting package?

Burble · 18-01-2007, 18:17

What particular SQL database?

Andy100 · 18-01-2007, 22:11

Thanks for the links, I think I'll have to do some more investigation into what SQL database it is.

I've only come on board half way through the implementation and it seems like there was no planning or project management done at all. It's a right balls up and I'm having to run the old accounting system (MYOB) in parallel just to have any idea of our correct financial position.

The accounting package is Epicor it's more an ERP than just an accounting package as it also manages our inventory, payables, receivables and payroll.

Andy100 · 18-01-2007, 22:19

Quote:

Originally Posted by Burbleflop

What particular SQL database?

I'm at home today so I've just had a root around on the Epicor website.

Would it be Microsoft SQL Server 2005 or Epicor SQL?

I've asked the consultants to come in and give me a days training. But they're pretty tight with their information so they can squeeze every last penny out of us.

Burble · 18-01-2007, 22:35

MS SQL 2005 I bet. Depending what you need to do, a days training is most likely not going to be enough. You'll have the SQL language itself (select * from tablename, and so on) and the MS quirkes to deal with.

Having access to do SQL straight onto the database has the potential to cause a lot of problems. If you're always going to be running the same queries, then ask about getting them installed as a stored procedure, that way rather than having to manually enter the SQL, you can just 'exec' the stored procedure and pass it any variables it needs.

Garp · 18-01-2007, 23:53

It should be possible, if you have Access, to be able to do a read-only link to the SQL Server, which would enable you to use Access's query UI to help you produce the information you need, and enable you to store common queries. Its been a long while since I used SQL Server though and I'm a might bit rusty on it. Most of my experience these days is with MySQL.

Burble · 19-01-2007, 08:59

The SQL Server Management suite has a pretty nice GUI based query editor (much better than the Access one). As far as read only access goes, that can easily be accomplished with a new user with limited privs. Of course though, the query may be doing some updates, in which case a read only user isn't going to be much use.

Most my my SQL experience these days in MySQL & Oracle. I've played a bit with SQL Server but gimme Oracle any day.

Mark · 19-01-2007, 12:06

If it is SQL Server, I'd recommend getting a second 'development' SQL server installed. Go here and download yourself either the trial edition (licensed for 180 days) or the express edition (free but significantly cut-down) to install on a seperate system. Find out how to make a copy of the live data on this system.

Now you have something you can experiment on without risk of breaking the 'real' system. If it does break, wipe the data and load a fresh copy.

*** Most Impostant if you do this *** - be sure you 'label' your systems in some way so that you can instantly tell them apart at all times (e.g. use a different user and password). One of the bains of an admin's life is having two identical systems and not knowing for sure which is which. I've known ISPs wipe out their entire customer email system (100,000+ users) because of misidentifying systems. Not good.

18-01-2007, 06:45	#1
Andy100 Nice weak cup of Earl Grey Join Date: Dec 2006 Posts: 48	What I don't know about SQL! Is just about everything and now I need to know it. Anyone have any good pointers on learning about SQL databases and how to query them? I'm the financial controller and we've moved our accounting package to a funky new SQL based one. There have been problems with the transfer and now it's costing us an arseload to call in the consultants to come in and, from what I've seen, do some pretty simple lookups. At the moment I'm a complete n00b but with your help! I know I can be a master within the week.

18-01-2007, 14:18	#2
Garp Preparing more tumbleweed Join Date: Jun 2006 Location: Hawaii Posts: 6,038	Umm.... Have you any experience of Microsoft Access? Strange question I'm sure, but when teaching someone SQL queries I've found it quite handy as I can get them to start with the query gui and then show them the SQL view of the query and explain through it. There is a pretty good tutorial here: http://www.w3schools.com/sql/sql_intro.asp __________________ Mal: Define "interesting"? Wash: "Oh, God, oh, God, we're all gonna die"?

18-01-2007, 17:59	#3
Jonny69 Noob Join Date: Oct 2006 Location: Socialist Republik of Kent Posts: 5,032	A gentle introduction to SQL: http://sqlzoo.net/ I found that quite useful for the basics. You learn quite quickly when you're working with it though. What's the accounting package? __________________

18-01-2007, 23:53	#8
Garp Preparing more tumbleweed Join Date: Jun 2006 Location: Hawaii Posts: 6,038	It should be possible, if you have Access, to be able to do a read-only link to the SQL Server, which would enable you to use Access's query UI to help you produce the information you need, and enable you to store common queries. Its been a long while since I used SQL Server though and I'm a might bit rusty on it. Most of my experience these days is with MySQL. __________________ Mal: Define "interesting"? Wash: "Oh, God, oh, God, we're all gonna die"?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

18-01-2007, 18:17	#4
Burble Rocket Fuel Join Date: Jul 2006 Posts: 7,826	What particular SQL database?

18-01-2007, 22:11	#5
Andy100 Nice weak cup of Earl Grey Join Date: Dec 2006 Posts: 48	Thanks for the links, I think I'll have to do some more investigation into what SQL database it is. I've only come on board half way through the implementation and it seems like there was no planning or project management done at all. It's a right balls up and I'm having to run the old accounting system (MYOB) in parallel just to have any idea of our correct financial position. The accounting package is Epicor it's more an ERP than just an accounting package as it also manages our inventory, payables, receivables and payroll.

18-01-2007, 22:35	#7
Burble Rocket Fuel Join Date: Jul 2006 Posts: 7,826	MS SQL 2005 I bet. Depending what you need to do, a days training is most likely not going to be enough. You'll have the SQL language itself (select * from tablename, and so on) and the MS quirkes to deal with. Having access to do SQL straight onto the database has the potential to cause a lot of problems. If you're always going to be running the same queries, then ask about getting them installed as a stored procedure, that way rather than having to manually enter the SQL, you can just 'exec' the stored procedure and pass it any variables it needs.

19-01-2007, 08:59	#9
Burble Rocket Fuel Join Date: Jul 2006 Posts: 7,826	The SQL Server Management suite has a pretty nice GUI based query editor (much better than the Access one). As far as read only access goes, that can easily be accomplished with a new user with limited privs. Of course though, the query may be doing some updates, in which case a read only user isn't going to be much use. Most my my SQL experience these days in MySQL & Oracle. I've played a bit with SQL Server but gimme Oracle any day.

19-01-2007, 12:06	#10
Mark Screaming Orgasm Join Date: Jul 2006 Location: Newbury Posts: 15,194	If it is SQL Server, I'd recommend getting a second 'development' SQL server installed. Go here and download yourself either the trial edition (licensed for 180 days) or the express edition (free but significantly cut-down) to install on a seperate system. Find out how to make a copy of the live data on this system. Now you have something you can experiment on without risk of breaking the 'real' system. If it does break, wipe the data and load a fresh copy. * Most Impostant if you do this * - be sure you 'label' your systems in some way so that you can instantly tell them apart at all times (e.g. use a different user and password). One of the bains of an admin's life is having two identical systems and not knowing for sure which is which. I've known ISPs wipe out their entire customer email system (100,000+ users) because of misidentifying systems. Not good.