I have a SELECT statement similar to the following:
SELECT YEAR(transaction_date) AS y,WEEK(transaction_date) AS w, COUNT
(*) AS c FROM transaction_data_view WHERE mid = 300
 GROUP BY YEAR(transaction_date),WEEK(transaction_date)

 how to design database for binary tree and insert and display values
from db. send me the querys

I have an entity that along with all of the usual attributes, has a
set of 140 bit flag attributes that I need to track all yes/no values
of. I started going down the path of creating a table 150 columns
wide, but after typing a few of them thought there may be a better

I'm currently working on a system that consists of several sites.  Each
site runs a system with its own local database, and then periodically
each site updates the "master" site with its data, allow the data to be
viewed centrally.

I just had an interesting discussion with a colleague regarding how we
are implementing search. We allow users to browse resources under a
list of topics, so for example a list of all resources relating to
'cars'. One way of doing this is with a SQL query against the database

I need to do "For each customer identified by Cust_ID sum last 90 days
of Sales from Monday for each Monday going back 365 days" and return
'Monday_Date', 'Cust_ID', 'Sales_Last_90_Days'.  I am going against MS
SQL Server 2000.  Need some help with the SQL.

Parts one, two and three have various mis-steps and confusions.  Let me
start again emphasizing what I think was McGoveran's paramount point -
the desire for logical data independence.  I interpret the meaning of
this in an algebra to be that substituting some non-logical aspect of ...

In the original exchange ( http://www.dbdebunk.com/page/page/1396086.htm 
  ), Date says:
"the operation DELETE SSP WHERE S# = S#('S1') AND P# = P#('P1') ;
is inherently unsafe, since we presumably don't know, in general,

I'm thinking about starting a hobby project.
I wrote a files-based Bulletin Board years ago.
I'd like to convert it to a more database-like system, so
password-identified users could edit old posts.

We are currently thinking of replacing our existing database system
which is no longer supported.
The data corpus encompasses 4 million records each of which having
about 30 fields. Half a million records would have a full text in PDF