Viewing 15 posts - 16 through 30 (of 35 total)
Good workaround, but that will help me for 1 table only (or small amount of tables).
Suposse I have Table01, Table02, ..., Table99 (99 tables).
I wanna be able to have a...
January 21, 2004 at 9:19 am
Thanks Calvin Lawson. The data is not stored sequentially. That is why I prefered to create a NON-clustered index with FILLFACTOR=50 so...
January 20, 2004 at 7:54 am
Yes, I agree with what you said; that is why I am using a different fliegroup located in a different container. I was not sure if it will behave as...
January 19, 2004 at 9:12 am
I was able to extract most of the tables.
I had problems with 5 of them, were they had the primary key clustered in a different filegroup (NDF). When I execute...
December 22, 2003 at 2:44 pm
MDF, NDF & LDF files were copied and then we tried to reattach the database. It did not work.
I created a database with the exact filenames in my local machine,...
December 22, 2003 at 10:40 am
Thanks fellows.
Frank, I will buy the book, but I am more confortable searching the web. I have started to maintain 5 SQL Server machines with not much time to read...
December 17, 2003 at 1:00 pm
After further RTFM (thanks jxflagg... i didnt know I was referring to pages) I learned that SQL Server will split the pages and move one of them into an empty...
December 17, 2003 at 11:53 am
Oh I forgot.
sp_lock will let me know the locks. How can I se which one is enqueued? (waiting for alocked resource)?
December 17, 2003 at 8:37 am
Thanks alpha3300,
We could not commit before executing the stored proc because the transaction was opened at the top of the vb, and in case of error it will rollback...
December 17, 2003 at 8:34 am
SQL92 and T-SQl give the same explain plan. Nested loop against the driving table (which is b).
Thanks all for your help
December 17, 2003 at 8:21 am
Thanks, I will try that.
The SIDs i am referring are the Session IDs on the database and their sql stamements.
December 16, 2003 at 1:29 pm
Just a note, that query will not use any indexes; so if your table is big, it will hit the performance with a full table scan instead of index scan....
December 15, 2003 at 3:16 pm
Guaranteed Range scan on col (if indexed)
SELECT col FROM tab WHERE col >= GETDATE() - 365
December 15, 2003 at 2:36 pm
Join update did the trick
UPDATE a
SET a = b.a,
b = b.b,
c = b.c,
d = b.d
FROM a,b
WHERE a.id = b.id
December 15, 2003 at 2:26 pm
Thanks Frank Kalis.
I really didnt think on that either. The article is clear with "not supported" clause.
December 12, 2003 at 2:12 pm
Viewing 15 posts - 16 through 30 (of 35 total)
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy