Viewing 15 posts - 47,401 through 47,415 (of 49,571 total)
What does the update statement do?
Can it be optimised to take less time? Can the indexes be tweaked so that it doesn't have to lock the entire table?
February 13, 2008 at 9:03 am
b_boy (2/13/2008)
Thanks GailIt basically means that db's ment for read only purposes can be cmpressed using the NTFS compression feature.
It's stronger than that. A DB on a compressed drive must...
February 13, 2008 at 4:24 am
Duplicate post. Replies to the following thread please:
http://www.sqlservercentral.com/Forums/Topic454929-23-1.aspx
February 13, 2008 at 3:38 am
SQL Server only supports read-only databases/filegroups on compressed drives.
See in books online under "File Backup and Restore and Compression"
February 13, 2008 at 3:26 am
This is assuming that's a full database backup you have there.
Open object explorer (F8), connect to your server.
Expand out the server until you see the folder Databases.
Right click -> restore...
February 13, 2008 at 2:58 am
Depends how fast your indexes get fragmented.
I've got a job that does a contig check on each table each week and records the results. It then will go and rebuild...
February 13, 2008 at 2:53 am
A proc has to be executed to appear in the procedure cache. Some of the things that can cause plans to be removed:
service restart (obviously)
sp_configure (some options when changed)
Alter Database...
February 13, 2008 at 2:50 am
I'm guessing the sysdate has a time with it? Datetimes always have a time portion that must be taken into account when comparing
You've got 2 options.
You can use a function...
February 12, 2008 at 11:05 pm
Anything sharing a server with SQL is not recommended.
Start with the RPC_Completed and Batch Completed events (under Stored procs and T-SQL respectivly)
Column - Text, cpu, reads, duration, start time,...
February 12, 2008 at 9:41 am
Look up CONVERT in Books Online. There should be an appropriate style for that.
February 12, 2008 at 9:36 am
The checkDBs that SQL runs on startup are not complete consistency checks of the entire database. I suspect it's just a check of the system objects.
DBID 2 is tempDB, but...
February 12, 2008 at 9:07 am
Is the application in question running on the SQL Server, or on another machine?
I would suggest profiler. Start a trace on the SQL Server and watch what the app's doing...
February 12, 2008 at 8:26 am
Hash matches happen in memory, unless the tash table gets too big. In that case, it spils to disk. It's called a hash bailout. There's an event in profiler that...
February 12, 2008 at 5:58 am
OOps. Sorry about that. That's what I get for answeringh over lunch without checking my syntax....
February 12, 2008 at 4:14 am
It works rather badly. There's a triangular join in there, with a correlated subquery. The combination will be hell for large rowcounts
February 12, 2008 at 3:08 am
Viewing 15 posts - 47,401 through 47,415 (of 49,571 total)