Viewing 15 posts - 50,776 through 50,790 (of 59,091 total)
peace2007 (5/3/2008)
Did you go buy the number of processors and create a files for each i.e if have 4 processors do you have 4 files for tempdb ..just curious.
So...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2008 at 8:56 am
You have a table with a single column and no external identifiers? Did you read the URL I pointed you to? You're not providing enough information for anyone...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 5:18 pm
First, take a look at the URL in my signature to get better help, faster. 😉
Following my own "rules", here some test tables and some test data...
--===== Presets
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 1:33 pm
In "old" SQL Server 2000, "schema" was actually called "owner". It's the login or role that owns the object. It's assigned when the object is created and defaults...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 10:07 am
I'm not sure what you mean by find all "month numbers" or "i want all the months inbetween to be listed"... do you want to find the first of every...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 9:53 am
Nicely done, Matt! I guess my only exception to what you said is that I use it to "replace loops" all the time. Although.... I'll agree that it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 1:17 am
Simon... take a peek at the following URL...
http://www.sqlservercentral.com/Forums/Topic494388-145-1.aspx#bm494619
Same technique can be used in SQL Server 2000 using VARCHAR(8000) with some limit, of course.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 1:05 am
This is a double post... please post any replies at the following URL...
http://www.sqlservercentral.com/Forums/Topic494354-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 12:59 am
I haven't tried it, but I believe your problem is in the following code...
DECLARE @MaxRecipeId as INT
SELECT @MaxRecipeId = MAX(RecipeId )
FROM Recipe Where LocationId =1
It should...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 12:57 am
I don't suppose you did a search on "running total" or anything like that... 😉
There's a lot of ways to solve the running total problem in SQL Server... they're all...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 12:50 am
Here's the proof...
DROP TABLE jbmtest
go
SELECT TOP 1000000
RowNum = IDENTITY(INT,1,1),
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 12:47 am
And, I gotta tell you, 2n for CHAR, VARCHAR, and NVARCHAR size doesn't make a bit of difference because row size isn't any multiple of 2n (ie. 8060) and neither...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 12:39 am
I'd have to say a lot of that depends on two things...
1. How important is the data? In other words, do you actually want the data to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 12:33 am
No, the order is predictable especially if you supress parallelism with MAXDOP... please see the following article...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
... and just say "NO" to cursors 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 12:17 am
Heh... yeech... you can use a cursor, if you like... here's your's with the fix...
DECLARE @MyCmd VARCHAR(100)
declare @database nvarchar(128)
declare mycursor CURSOR LOCAL
FOR select name from master.dbo.sysdatabases where dbid>5
OPEN mycursor
fetch...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2008 at 12:01 am
Viewing 15 posts - 50,776 through 50,790 (of 59,091 total)