Viewing 15 posts - 42,781 through 42,795 (of 59,098 total)
Almost forgot... it would be a help if you attached the CREATE TABLE statment for your table as a text file. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2009 at 6:47 am
In my example, AddressID would be the same as your two columns, ParticipantID and RowID.
On your other question, while some bit of unexpected notoriety has come of it, I do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2009 at 6:45 am
I believe that Lamprey's solution with the Tally table will do what you need. For more information on what a Tally table is and how it can be used...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 9:02 pm
Herbie (7/23/2009)
Ok thanks for your inputs... i think same with tempdb will do go for raid1
TempDB doesn't need any redundancy... it get's rebuilt every time you reboot.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 8:57 pm
Ditto.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 8:52 pm
I believe that what you're looking for is "Replication". There are several forms of "Replication". Look them up in Books Online to see which form would suit you.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 8:51 pm
Heh... Lots of folks scoff at it but I prefer to save just the file names of images in a database. The images are stored as 1 file per...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 8:48 pm
Any feedback on this problem?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 8:33 pm
jeschumm (7/23/2009)
Thanks so much for your advice! I did some research on parameter sniffing (which I have to admit I'd never heard of) and found a great example of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 8:25 pm
[font="Courier New"]DECLARE @table varchar(100), @sql varchar(2000)
SET @table = 'sometable'+left(convert(varchar,dateadd(dd,-2,getdate()),112),6)
SET @sql = '
SELECT rid, username FROM OPENQUERY(linked_server,''SELECT rid, username FROM database.[highlight]dbo.[/highlight]'+@table+'
WHERE rid '''''''';'')
'
EXEC (@sql)[/font]
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 8:17 pm
The number of rows probably didn't increase... they're just being reported more accurately because the new clustered index takes over as the reported rowcount.
I'd peel one potato at a time......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 8:08 pm
SQL Server exercises it's own locking. Why do you want to override it?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 7:58 pm
Are you suggesting that the users generate all 18 lakhs of rows 30 rows per page in a single report? I suppose there are a lot of options but...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 7:32 pm
"RAW"
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 7:25 pm
I'll second that.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2009 at 7:23 pm
Viewing 15 posts - 42,781 through 42,795 (of 59,098 total)