Viewing 15 posts - 55,996 through 56,010 (of 59,072 total)
That too, will work, but as Chris Morris pointed out, any time you do a calculation/function on a column in the WHERE clause, you will decrease performance (A LOT!!) if a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2007 at 7:49 am
I found this in Books Online...
When the IDENTITY property is used with CREATE TABLE, Microsoft® SQL Server™ uses the NOT FOR REPLICATION option of CREATE TABLE to override the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 10:12 pm
Um... I gotta ask... why wouldn't 0.3333 represent all of the numbers from 0.3332(5) to 0.3333(4) in the TR model?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 9:50 pm
Well, maybe an Index Scan... but you're (almost) exactly correct... the OR in this case will certainly allow an Index SEEK to occur if the correct index is available.
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 6:21 pm
No, David... JacekO did it just right... try it and see...
--===== Declare and populate a test table
DECLARE @test-2 TABLE (RowNum INT IDENTITY(1,1), SomeString VARCHAR(10))
INSERT INTO @test-2 (SomeString)
SELECT 'A'...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 6:10 pm
Like I said earlier to your core question... "Yes".
It's just a bad idea to shrink files that are destined to grow again because of file fragmentation. You must first...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 5:45 pm
No problem, Noel... it's easy to see how I might have been taken because I was pretty adamant about the whole IDENTITY thing. ![]()
So,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 5:31 pm
Eamon,
I was a bit out of line... I should have asked why you need to do this so we can come up with the best solution for your circumstance.
So,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 5:02 pm
So... someone wanna ask the OP what's up?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 5:01 pm
You can protect your database if you create it as a separate instance of SQL Server and make "linked servers" for the client to yours... of course, linked servers create...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 7:15 am
Sorry... not familiar with either the tool or the product, Lakshmi.
Can anyone else help Lakshmi?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 7:11 am
Does it support the following query?
SELECT * FROM SysIndexes
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2007 at 6:51 am
In that case, the answer to your original question is "YES".
I suppose I shouldn't mention it because it is outside the original question, but shrinking the file and having it...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2007 at 7:01 pm
None... we don't use replication for replication ![]()
Anyway, wasn't meant to be a challenge, Noel... was just curious.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2007 at 6:41 pm
If it's mission critical as you say, why not just buy some more harddisk space? That's a lot cheaper than losing data...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2007 at 2:51 pm
Viewing 15 posts - 55,996 through 56,010 (of 59,072 total)