SQL Server query

semaphore said:
Whenever i see an SP i feel like ive been raped. This one SP i ran across had 4,000 lines in it.
Click to expand...

That's not because of stored procedures. It's bad programming. You may as well also say you will never use a select statement because a badly written select statement bring any database down to a grinding halt.
 
zippy said:
That's not because of stored procedures. It's bad programming. You may as well also say you will never use a select statement because a badly written select statement bring any database down to a grinding halt.
Click to expand...

No actually your analogy is totally off you're equating syntax to design methodologies that should have died out years ago.
 
Batista said:
I agree,a programs logic shouldn't exist in the db.I like to separate my programs into GUI/Data/logic,but what are you using to query your db then?Something like MS entity or a doodad?You cant write SP off for good, they have their place.
Click to expand...

It depends on the project, and no EntityFramework is slow, very slow.

And yes i can write off SP for good and have i'm pretty sure i have established this in my previous posts. ;)
 
semaphore said:
It depends on the project, and no EntityFramework is slow, very slow.

And yes i can write off SP for good and have i'm pretty sure i have established this in my previous posts. ;)
Click to expand...

Lol cool, but the reason i asked what you are using instead of SP is that we need to now move away from doodads and i do not want to use MS entity?
 
stored procedures have their place if done correctly.

now cursors in stored procedures -> thats the real evil right there
 
multiple posts of "having business logic in your database is good"

1620742673_532dd66d_mind_blown_xlarge.jpeg
 
If I may ask a noobish question... If you require a result set for a report, for example, with multiple joins from different tables, how would one go about doing that in code? Would you manually create the dataset and manipulate it? I like the idea of reducing strain on the SQL server.
 
There is nothing wrong with SPs semaphore, no matter how much you hate them... They have their place, as do Views, as does inline sql, as does everything.
 
ToxicBunny said:
There is nothing wrong with SPs semaphore, no matter how much you hate them... They have their place, as do Views, as does inline sql, as does everything.
Click to expand...

Cool. I totally disagree but we'll agree to disagree, but most likely disagree anyways ;)
 
paddy_za said:
If I may ask a noobish question... If you require a result set for a report, for example, with multiple joins from different tables, how would one go about doing that in code? Would you manually create the dataset and manipulate it? I like the idea of reducing strain on the SQL server.
Click to expand...

Depends on a few things, infrastructure, reporting tool, etc.
 
semaphore said:
Cool. I totally disagree but we'll agree to disagree, but most likely disagree anyways ;)
Click to expand...

I figured we'd disagree, but it is the truth... if they had no place then the people developing the systems would be deprecating the features.
 
ToxicBunny said:
I figured we'd disagree, but it is the truth... if they had no place then the people developing the systems would be deprecating the features.
Click to expand...

Obviously they aren't going to start reducing feature sets in DB's. That would be well just daft.

But its like saying lets rather poll a url every 2 seconds, i mean this is how it used to be done lets keep doing it that way or we could move ahead with the times and use something like websockets.
 
iceman23 said:
stored procedures have their place if done correctly.

now cursors in stored procedures -> thats the real evil right there
Click to expand...

Surprised it took 3 pages to mention this :p SP with a cursor to build some dynamic sql ftw
 
semaphore said:
Obviously they aren't going to start reducing feature sets in DB's. That would be well just daft.

But its like saying lets rather poll a url every 2 seconds, i mean this is how it used to be done lets keep doing it that way or we could move ahead with the times and use something like websockets.
Click to expand...

Ummm they reduce feature sets with every release, whilst introduce new features...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X