Viewing 15 posts - 39,991 through 40,005 (of 59,072 total)
Another good idea. Thanks Wayne. Just curious though... have you ever used it that way?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 9:00 pm
Why wouldn't UNPIVOT (maybe, more than one) do the job here?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 8:59 pm
It's ironic... as someone once said, "The more things change, the more they stay the same". Holy shades of "RAM DISK", Batman! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 8:55 pm
mohaminho10 (2/1/2010)
It is actually going to update more that 5 DB's...the total runs to about 25 DB's.Does anyone have a sample code that I can take a look at?
Thanks
Simple...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 6:28 pm
Rebuild the clustered indexes, shrink the MDF, rebuild the clustered indexes again. Won't help the LDF, though.
As a side bar, unless these so-called "space cleaners" do overwrites with all...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 6:25 pm
Ummmm.... what would be so bad with doing a BCP "Native" export for the month data involved? It would simplify things quite a bit.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 6:00 pm
Absolutely. See the following link. Almost exactly what you need...
http://www.sqlservercentral.com/articles/Crosstab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 5:51 pm
Would the default trace do what you want???
Also, I'm curious... is this a requirement to meet a "spec" for something like SOX compliance or do you just distrust your DBAs?...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 5:47 pm
If i have to move databases from one machine to another, I also make the assumption that I need to do at least the daily maintenance of defragging/rebuiding indexes that...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 5:24 pm
george sibbald (2/1/2010)
Steve Jones - Editor (2/1/2010)
If you're using RDP, network isn't an issue.Stats should move, but as Jeff mentioned, they often don't seem to in a backup/restore.
I thought Jeff...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 5:16 pm
Digs (2/1/2010)
Is that wise ???
For example I have one column filled with BIT or -1 or 0
Shouldnt need to sort that !
When is it wise...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 5:12 pm
John Rowan (2/1/2010)
Best practice is to index your FK columns for join performance.
CREATE INDEX <index name> ON <table name>(<column name>)
The FK's should probably be on the PK of the "remote...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 5:11 pm
GilaMonster (2/1/2010)
Please post the query, table definitions, index definitions and execution plan as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
This will probably be something fairly easy to fix but unless you can help us help...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 5:09 pm
First, table partitioning is an "Enterprise Edition" option. If you don't have the "Enterprise Edition", it's not an option.
If you don't have the "Enterpise Edition", you could make a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 4:57 pm
I'm not a hardware person by any means but if the server can actually take more memory and SQL Server can actually use it (meaning that both the OS and...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2010 at 4:38 pm
Viewing 15 posts - 39,991 through 40,005 (of 59,072 total)