| Author |
Topic |
|
yoggi123
Starting Member
29 Posts |
 Posted - 2005-03-09 : 06:46:20
|
| Hi,For the past few months I have been developing reports using SQL Server only, but just recently I was assigned to a new client who needs reports created using a Oracle database. I have never used Oracle before in any fashion, so I was wondering about connections to the Oracle database, how the coding will differ, etc. My biggest concern is with the coding, I mostly have used stored procs to produce the reports, so I am wondering how this would change with a Oracle database, or if there would be any change at all, will the be syntax changes, etc.Any info would be good right now.The client also asked me to research on how to connect Reporting Services to the Oracle db, any ideas on this would be appreciated as well.Thanks |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-03-09 : 07:07:18
|
| If you are Brand New to Oracle allow MUCH longer than you are expecting to get proficient at it. (By "proficient" I mean good enough to deliver something "Robust" to a client, not the time to become an Oracle God - whcih is best measured in Eons ...)I have always been astonished at how long it takes to tune and sort out things in Oracle, compared to SQL Server. I'm much more familiar with SQL Server - but it sounds like you are in the same boat.Even stuff I ahve done on client's sites with their Oracle DBA God doing the grunt takes way longer than I can do it in SQL Server. Things like creating a database from a script. Some database settings get in the way - and they'll be critical to other databases the client is running on that server; or the client has promised the Oracle server will be a Windows box, but actually they move it to a Unix box at the last minute and all the CR/LF in your Windows-originated file are now getting in the way. All sorts of junk like that. Happens every time I go near Oracle.Equivalent to SProcs, Performance tuning, Ways of doing Backups and Housekeeping : All very different.Someone by all means shoot me down and put me right - I'll be thrilled to hear itKristen |
 |
|
|
yoggi123
Starting Member
29 Posts |
Posted - 2005-03-09 : 07:19:27
|
| I am supposed to be finished by the end of April, but it sounds like I have much to learn first, this might be interesting. |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-03-09 : 07:59:50
|
| If you're just reporting, you don't have to worry about backups and other maintenance, and you probably won't have to learn too much about designing and optimizing the database (you won't be able to change it much anyway).The biggest difference is Oracle's SQL syntax, it's different from SQL Server's in significant ways. I never used Oracle stored procedures, but they are different as well (variable names, etc.) I think if you got an intro book on Oracle or found some good online documentation (good luck) you'll pick up enough to do reports in a fairly short time. |
|
|
|
yoggi123
Starting Member
29 Posts |
Posted - 2005-03-09 : 08:24:48
|
| Hi,That sounds about right, I just need to know how to build the reports using an Oracle db, so mostly I'll look around for syntax differences.From the building reports perspective, what am I going to need on my local machine and how am I going to connect to the Oracle db, is there anything much different then from SQL?One more thing. For the most part I have used stored procedures for my reports, am I the minority for doing this, is there a better way to do things? I am asking this because it seems like not many other people do. Any suggestions?Thanks |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-03-09 : 12:29:24
|
| From within Reporting Services, you'll setup a data source that would use an Oracle driver to get to the Oracle server. I also use stored procedures for my reports.Tara |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2005-03-09 : 12:34:55
|
| Stored procedures for mostly everything.So you're not going to be coding in Oracle?What version is it btw?EDIT: Alos I imagine that if the SQL gets pretty hairy, you'd be much better of coding stored procedures and packages in Oracle so the work can be done on that server. Otherwise you could bring the network in to play and move lots and lots of data that you don't want.Brett8-) |
|
|
|
yoggi123
Starting Member
29 Posts |
Posted - 2005-03-09 : 14:46:19
|
| Ya, I am thinking the same thing right about now. Just got to get the syntax differences down path first. I just installed the Oracle Developer Tools for Visual Studio .NET Beta 2, so I think that could be really helpful to me if they work like I hope they do. Are the syntax differences a really big deal? Anyone know of a good site that would be useful for reference and beginner learning?Thanks |
|
|
|
Kristen
Test
22859 Posts |
|
|
dbaperson
Starting Member
2 Posts |
Posted - 2005-03-21 : 12:35:16
|
There is a good paper with comparison between Oracle and SQL Server.It compares mostly Yukon and 10g though : http://www.wisdomforce.com/dweb/resources/docs/MSSQL2005_ORACLE10g_compare.pdfquote:
Originally posted by yoggi123
Hi,For the past few months I have been developing reports using SQL Server only, but just recently I was assigned to a new client who needs reports created using a Oracle database. I have never used Oracle before in any fashion, so I was wondering about connections to the Oracle database, how the coding will differ, etc. My biggest concern is with the coding, I mostly have used stored procs to produce the reports, so I am wondering how this would change with a Oracle database, or if there would be any change at all, will the be syntax changes, etc.Any info would be good right now.The client also asked me to research on how to connect Reporting Services to the Oracle db, any ideas on this would be appreciated as well.Thanks
|
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-03-21 : 20:20:18
|
| More accurately, it accentuates "flaws" in SQL Server (flaws being anything that Oracle does but SQL Server 2000 doesn't, at least not by default) and then talks about how well Oracle does these things today, while you have to wait until SQL Server 2005 to get relief. About as balanced as a drunken epileptic elephant doing a high-wire act on roller skates. |
|
|
|
|
SQL Server vs Oracle