Viewing 15 posts - 13,876 through 13,890 (of 14,953 total)
From the example given, I'd say the easiest way to do this would be:
select *
from dbo.Table
where Column like '%Reg%'
If you really need something smarter than that, then you need to...
May 5, 2008 at 7:58 am
Because of the way views work, think of them as a way to give yourself a shortcut for complex queries that you will use over and over again.
So, the answer...
May 5, 2008 at 7:50 am
Enterprise Edition requires a server OS.
If you're planning on using it only for personal use, or for dev use, you can use SQL Server Dev Edition on Vista. That's...
May 5, 2008 at 7:38 am
Use a temp table instead of a CTE for this. CTEs can't have procs in them.
May 5, 2008 at 7:35 am
select 1
while @@rowcount > 0
... your update script here ...
Or you can use "While exists ()". Put the query you want inside the parentheses.
May 5, 2008 at 7:34 am
So, basically you don't back up the database, and someone deleted a system table that you need?
I'm really not sure what to do about that. I tried a Google...
May 5, 2008 at 7:32 am
MSDN.com has tutorials with walk-throughs for this kind of thing.
Volunteering to help a church or other charity is a good idea.
Another is to find something in your own life that...
May 5, 2008 at 7:29 am
It looks okay to me too. I'd try running each sub-query separately. See if they all work on their own.
May 5, 2008 at 7:22 am
If all the proc does is select stuff, you could always have the scheduled job that updates the statistics run the proc as a second step. Would that work...
May 2, 2008 at 9:52 am
I don't see an error in either of these. Can you post the whole proc that's giving you the error?
May 2, 2008 at 9:48 am
SQL Server 2005 Bible (Wiley Publishing) by Paul Nielsen, has very good data on that (and a ton of other data).
May 2, 2008 at 9:45 am
Viewing 15 posts - 13,876 through 13,890 (of 14,953 total)