sql server 2005 vs 2008

[almagg]

i want to start working with sql server.
i see a lot of jobs that want Excel programming along with sql server skills.
so i need to be able to work with an existing sql server setup, not actually build a platform.

i have XP Home - SP3
i have seen there is a 2005 version for SP3. i believe before that there were some bugs.
and i read somewhere that 2005 will not be supported after i think april 2011.
are there any major differences.
will the majority of companies still stay with 2005?

anyway here are two sites for downloading.
thanks for any advice.

2005
http://www.microsoft.com/downloads/...2A-4090-4431-ACDD-9A1C832E65A6&displaylang=en

2008
http://www.microsoft.com/downloads/...83-4cb2-454e-b908-e805e9bd4e28&DisplayLang=en

 

[dk]

Hi

If you want to learn the basics then download the SQL Server Express edition (2008) and go from there. In terms of learning how SQL server works, how to set up a database and how to get Excel to interact with the database then that would be enough. Do the jobs that you're looking at require some DBA skills or is it more retrieving data from the database into Excel?

In terms of support, the April 2011 you're referring to is only relevant if you haven't updated to the latest service pack. If you're on service pack 3 then support is still ongoing and will be in the forseeable future. Although if you're only looking to download the free edition to learn how it works then I wouldn't really worry about support!

HTH
DK

 

[almagg]

well i have seen requirements for both someone with high DBA skills and others that the SQL needed is just for the purpose of getting the data from the server.
right now, since i have the advanced Excel programming background i am going to stick with the latter.

i also see a lot more need for Excel interaction with Access.
i know Access and can use the GUI to create complicated queries.

anyways i have never actually hard-coded SQL but i can read it when i see it and know what
left/right joins are etc...

so i figure to start becoming familiar with SQL server which at the same time will make me start writing SQL code from scratch.

appreciate the comments.

 

[xenou]

Write your sql for Access too I use a text editor with SQL highlighting -- notepad++ -- and then copy it into Access SQL view (since the Access text editor is very poor). Which is to say, if you're already using Access frequently then you have a great opportunity for practice and it should not be missed.

 

[almagg]

good idea.

i have not used Access recently meaning i have to get up to speed on the 2007 layout.
but the querying looks the same. it is one of those instances where a lot has to be learned at once. i have the foundation but still a lot of work. i also will need to start learning Access VBA code since if I am going to communicate from Excel I will have to learn the OLE and various other Access code.

the jobs i see are mixed. and the only things i am lacking are the SQL server and the Access programming (to use existing databases). and they are usually separate requirements i.e., one or the other is needed.

now if i am going to write the same queries in Access, whatever db i am using in SQL server would have to be in Access for me to check the results. yes? know what i mean?

i am not clear on the "...text editor with SQL highlighting...notepad++..."

 

[Norie]

Why would the database need to be in Access to check the results?

xenou is just referring to a text editor that has some extra functionality that
helps when creating SQL. eg highlighting syntax problems

If you are writing queries in SQL Server via something like the Management Studio then I think the syntax etc will be checked.

It certainly was for me recently when I created some code to create a database, create tables in it and then populate them.

Mind you I was sort of cheating using some SQL from MySQL.

Found out quite a few things about the differences between SQL Server and MySQL syntax, data types etc

 

[almagg]

ok, i understand what you are saying.
much like the Excel VBA editor checks the code syntax as it is written.
so by copying one SQL code into a text editor which handles say Access, i would be alerted to "errors" thus learning the differences in syntax.

something like RazorSQL
i just did a search for "access sql text editor" and got hits.

thanks. this is good.

 

[Norie]

I think you are sort of getting the idea.

As far as I can see the application you menu is just a tool to help you write SQL.

Different databases have different 'flavours' of SQL and therfore can have different syntax.

The syntax won't be radically different across the 'flavours', it could just be things like how strings are handled, how to use date etc.

Some will be stricter than others.

If you like a tool like RazorSQL brings them together in one place which could be useful, perhaps when the database being used is to be changed.

Most databases have their own way of doing this sort of thing or something similar.

When working with a particular database it might be best to actually use that built-in functionality.

A product like RazorSQL may be useful but it might not be able to check things as well as the database itself.