Tag Info

Hot answers tagged

6

No, because you need at least basic IO capabilities to be able to serve up web content. Assuming you finesse that by using something else to put in front of your database server then, yes, technically that would be possible. It would just be horrible.


3

It is a matter of opinion. You might use postfix representation (à la RPN, or even some stack-oriented programming language), or some bytecode (specific to your expression language), or some s-expr syntax, if you want some more compact representation. JSON is probably a less compact textual representation but it is very widely used (and you've got many ...


2

Why not put configurable text logging into the C++ product. You can then write a separate program (in any language) to consume the log offline, or in real time, and populate a SQL database. This will decouple the SQL/DB requirement from your C++ code base, and you won't have to compile & link against or even install SQL on most machines. For the ...


2

Since you have the primary key of each record, I highly recommend using the approach of examining each record individually. Primary key lookups are extremely fast in any professional-grade database. Updating a record based on primary key has a very granular lock level and is fast. By inserting or updating rather than delete/insert, you maintain the ...


1

Well, there are a whole lot of things to consider here, some of which you touched on. First, why are you moving this to a program rather than a SQL script? Do you need to run this from machines that don't have SQL? Have you considered that you'll likely need SMO and other pre-reqs on the machines anyway (meaning it wouldn't be difficult to just have SMS ...


1

Sounds like your intent is to capture the existing functionality in a test case before making changes, which is the smart way to go. Tested code == good code. Check out this question over on Stack Overflow, it may help point you in the right direction.


1

I agree with Snowman and think you should do all the queries. Along with performance being negligible, you can gain some insights about the data changes that may benefit you and/or users: New Categories Removed Categories Categories that have changed. Someone is eventually going to ask what happened. "We got a new file," won't be enough.


1

If you data requirement is the joined data (solution 2) then tailor your stored procedure for that data. Overly reusing a bunch of stored procedures that are select * from table is best case... cumbersome and worst case... high performance impact (think, pulling back more data than you need over the wire). Let the relational database management system do ...


1

Yes, I have seen significant performance problems result from this sort of pattern. If you have branches in your sproc that result in making significantly different queries, under certain circumstances this can cause huge performance problems. SQL server will build an execution plan for a sproc when it needs to based on the values of the parameters passed ...


1

You raise Apache specifically, so I will discuss this in detail. Apache can be configured to log to a database, although it requires an external plugin to do so. Using such a plugin can make log analysis easier, but only if you intend to write your own log analysis software. Standard off-the-shelf log analysers assume your logs are in files, so you won't be ...



Only top voted, non community-wiki answers of a minimum length are eligible