Comments on: My SQL2005 Diary – Part1 http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/ Ethical Hacking, Penetration Testing & Computer Security Tue, 14 Feb 2012 00:17:07 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Haydies http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/#comment-386 Haydies Thu, 30 Mar 2006 11:08:08 +0000 http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/#comment-386 Ok, my 10 pence worth. Crystal reports is garbage, always has been, always will be. If it dosn't crash it corrupts reports, one version wont modify another versions files... its generaly slow, clunky and well, there are so many better options. "including some very cool stuff that is new to database servers as a whole", also not true. Oracle has been able to have embeded Java code for some time. It can even store "active" Java objects. Ok, my 10 pence worth.

Crystal reports is garbage, always has been, always will be. If it dosn’t crash it corrupts reports, one version wont modify another versions files… its generaly slow, clunky and well, there are so many better options.

“including some very cool stuff that is new to database servers as a whole”, also not true. Oracle has been able to have embeded Java code for some time. It can even store “active” Java objects.

]]> By: tonyenkiducx http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/#comment-363 tonyenkiducx Wed, 29 Mar 2006 07:53:18 +0000 http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/#comment-363 Dzof - We literally do 90% of our work in the SQL layer and its a lot more than just reporting(I did mention we use reporting services for our reporting though). For example, if a customer at a hotel in south africa wants some flowers sending to his room, the desk clerk there puts it in his computer through our webapp, and it is instantly added to his file in the UK as a surcharge to his current holiday, his credit line is checked(Whatever it might be, credit score, credit card, direct debit), and authorization sent back to the clerk(Or a request for a cash payment), an extra invoice is queued in the letter batch for that night to be printed and sent and a sales rep has the file flagged in there list so they can check it to make sure that everything is ok. All of that is done by the SQL server. Darknet - The RAM thing in SQL is always a worry for people who dont use SQL server a lot, it does like to run away and steal RAM when it can, but with a bit of experience(No offense meant) you can easily manage that problem. The Americans use oracle, but even they are now moving away from it because of the prohibative costs(More on the costs in part 2). Your right that in an ideal world we would have an application layer in between the web app and the data later, but unfortunately the system were working on was designed and built by someone who had never even seen the internet before and just had a copy of dreamweaver, so they stuck with what they knew and went 99% sql. Its not ideal, but I have to admit it feels much neater and easier to have everything in 1 language and in 1 place. Dzof – We literally do 90% of our work in the SQL layer and its a lot more than just reporting(I did mention we use reporting services for our reporting though). For example, if a customer at a hotel in south africa wants some flowers sending to his room, the desk clerk there puts it in his computer through our webapp, and it is instantly added to his file in the UK as a surcharge to his current holiday, his credit line is checked(Whatever it might be, credit score, credit card, direct debit), and authorization sent back to the clerk(Or a request for a cash payment), an extra invoice is queued in the letter batch for that night to be printed and sent and a sales rep has the file flagged in there list so they can check it to make sure that everything is ok. All of that is done by the SQL server.

Darknet – The RAM thing in SQL is always a worry for people who dont use SQL server a lot, it does like to run away and steal RAM when it can, but with a bit of experience(No offense meant) you can easily manage that problem.

The Americans use oracle, but even they are now moving away from it because of the prohibative costs(More on the costs in part 2). Your right that in an ideal world we would have an application layer in between the web app and the data later, but unfortunately the system were working on was designed and built by someone who had never even seen the internet before and just had a copy of dreamweaver, so they stuck with what they knew and went 99% sql. Its not ideal, but I have to admit it feels much neater and easier to have everything in 1 language and in 1 place.

]]> By: Darknet http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/#comment-360 Darknet Wed, 29 Mar 2006 06:49:40 +0000 http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/#comment-360 Ah MSSQL becomes a truly transactional database finally.. Should alleviate some of the load problems anyway...I always found it a resource hog though, needs some massive amounts of RAM. Sounds like a fairly monster project anyway.. Did your guys not think of moving to Oracle to avoid this problem again with scaling in the future? I guess you don't have a data abstraction layer though...so it's all fairly MS-SQL dependant. Ah MSSQL becomes a truly transactional database finally..

Should alleviate some of the load problems anyway…I always found it a resource hog though, needs some massive amounts of RAM.

Sounds like a fairly monster project anyway..

Did your guys not think of moving to Oracle to avoid this problem again with scaling in the future?

I guess you don’t have a data abstraction layer though…so it’s all fairly MS-SQL dependant.

]]> By: Dzof http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/#comment-358 Dzof Wed, 29 Mar 2006 06:08:55 +0000 http://www.darknet.org.uk/2006/03/my-sql2005-diary-part1/#comment-358 Aha. May I step in here and suggest that instead of handcoding SQL statements, you use a reporting program - like, say, Crystal Reports - to come up with the goods? Of course the fact that I give training in this area doesn't make this comment self-serving in any way whatsoever... ;) Honestly, though, if you're building extremely complex SQL statements to then present results to end-users, it would be worth investigating reporting tools. Even if it is (*cough*) <i>MS SQL reporting services</i>. Aha. May I step in here and suggest that instead of handcoding SQL statements, you use a reporting program – like, say, Crystal Reports – to come up with the goods?

Of course the fact that I give training in this area doesn’t make this comment self-serving in any way whatsoever… ;)

Honestly, though, if you’re building extremely complex SQL statements to then present results to end-users, it would be worth investigating reporting tools. Even if it is (*cough*) MS SQL reporting services.

]]>