Viewing 15 posts - 331 through 345 (of 663 total)
In general : never make an assumption about the sequence in which data will be returned from a query.
July 10, 2003 at 9:44 pm
An alternative is, if the bit values do not change to 'often' use a view and a trigger that will redefine the view when a bit is flipped. Assumption: often...
July 9, 2003 at 5:29 pm
Hi, a5xo3z1, after reading the two posts it made me think of some maintenance work done awhile back where the business rules got a bit lost after multiple mods and...
July 8, 2003 at 11:50 pm
Different horses for different courses.
In the run off the mill databases one do not see such level of dynamics very often.
If you do not switch columns on/off to often I...
July 8, 2003 at 11:37 pm
Any other documentation for maintenance purposes, business rules, etc. ?
July 8, 2003 at 3:08 am
Problem similar to the paging requests of an ASP page through a recordset. Other words want records 100 to 109, then 110 to 119 or backwards 90 to 99, etc.
July 8, 2003 at 2:44 am
How about a startup proc to create an entry in a table with a start_column = getdate() and with a sheduled job running every 5 min updating the last row,...
July 8, 2003 at 2:34 am
Start looking at Query Analyzers templates.
Haven'nt used it myself, but one can specify templates in QA.
July 8, 2003 at 2:16 am
No help to solving your problem
http://dbforums.com/arch/70/2002/11/549598
Maybe one them have found a work around.
July 4, 2003 at 12:26 am
July 3, 2003 at 11:18 pm
July 3, 2003 at 8:49 pm
How about a scheduled job that can get activated on request?
July 3, 2003 at 6:32 pm
Belov thanks for the example.
Mdamera look in C:\Program Files\Microsoft SQL Server\MSSQL\Upgrade
July 3, 2003 at 6:29 pm
Viewing 15 posts - 331 through 345 (of 663 total)