Viewing 15 posts - 57,376 through 57,390 (of 59,067 total)
According to the datasheet available at:
Subqueries are allowed and parameters are allowed...
Compact Yet Capable
SQL Server Mobile offers rich relational database functionality in the small footprint necessary...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2006 at 8:39 pm
Crud... didn't see it before but Vladan beat me to the explanation for Cory a long time ago... sorry.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2006 at 8:03 pm
Because GETDATE() has a time associated with it. The want all of yesterday... in order to do that, you must strip the time back to midnight of yesterday... all that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2006 at 8:02 pm
There's probably a dozen ways... here's a couple without UDF or Tally table...
declare @table table (ad_str1 varchar(50))
insert @table
select 'apple avenue w' union all
select 'melon road e' union all
select...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2006 at 7:54 pm
Junkie,
Would you post the query that creates the example output that you posted? I think that's probably the key, here.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2006 at 6:42 pm
Nicasio,
In order for the EXE to release it's grip, it must close connections, destroy the connections, AND successfully exit the command processor window you've invoked. When you run it as...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2006 at 6:35 pm
What ever you make with a permanent table, should also work with a temp table except FK constraints. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2006 at 6:05 pm
Actually, Martin gave you the previous answer... but thank you, anyway.
I've not had the time to "play" with it, but you are missing a column alias in your stored procedure which...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2006 at 12:35 am
Absolutely outstanding article, Sushila... Your fine article should be the one that is required reading, not only for the "newbies", but for many of us old hacks as a reminder...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2006 at 11:01 pm
Long term transactions will cause huge wait periods and, possibly, deadlocks. I like Sreejith's method and have used it before... we used a column called "IsDirty" and it contained the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2006 at 8:38 pm
| I am running a stored procedure that uses a cursor (I know, I know, I couldn't find a... |
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2006 at 8:25 pm
The way you have it written, you are trying to insert into a temp table and variables at the same time. If you want to do both, you will need...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2006 at 8:21 pm
Be aware that when you change a diagram and save it, it actually updates your database to match... diagrams are really a form of somewhat anorexic data models.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2006 at 8:16 pm
Another possibility would be to use a "Linked Server" which would also hide the login and password from prying eyes.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2006 at 8:14 pm
That's a good start... got any data we can play with and, like I asked, are the tests stored in the same table as the quizzes? If so, what marks...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2006 at 4:54 pm
Viewing 15 posts - 57,376 through 57,390 (of 59,067 total)