Viewing 15 posts - 38,716 through 38,730 (of 49,571 total)
GSquared (6/3/2009)
June 3, 2009 at 9:41 am
SQL runs on a server. If the trigger were to pop up a message box, where do you think it would pop up?
June 3, 2009 at 9:24 am
Jules Bonnot (6/3/2009)
June 3, 2009 at 9:20 am
Jules Bonnot (6/3/2009)
Hi would you mind expanding your post a little.What are the disadvantages of having heaps.
Forwarding pointers and the resulting increase in IO. Only an issue when there...
June 3, 2009 at 8:07 am
Simon_L (6/3/2009)
p.s is that the babylon rangers motto I see ?
Yup.
June 3, 2009 at 7:46 am
Duplicate post. No replies to this thread please. Direct replies to:http://www.sqlservercentral.com/Forums/Topic728028-357-1.aspx
June 3, 2009 at 7:46 am
rvz (6/3/2009)
June 3, 2009 at 7:30 am
Eswin (6/3/2009)
SQL Server doesn't immediately shrink log files when you issue the DBCC Shrinkfile command.
Yes it does. When you issue a SHRINKFILE, the file in question is shrunk. How...
June 3, 2009 at 7:27 am
In my opinion, yes. Every table should have a clustered index. There are a few disadvantages to having heaps. That said, a badly chosen clustered index is worse than no...
June 3, 2009 at 7:26 am
Simon_L (6/3/2009)
June 3, 2009 at 7:23 am
sateesh.kamalakar (6/3/2009)
June 3, 2009 at 7:09 am
bhuvnesh.dogra (6/3/2009)
But how would you go for JOBs migrations ?????
Method 1:
Script the jobs out, run the script on the new server
Method 2:
Use the SSIS Transfer Jobs task.
Either way, jobs...
June 3, 2009 at 7:08 am
I would still do some analysis before dropping them, ie review stored procs and views and make none of them would need that index.
June 3, 2009 at 2:40 am
Eswin (6/3/2009)
always issue checkpoint before executing dbcc shrinkfile ().
Why?
June 3, 2009 at 2:35 am
Why do you want to shrink? Databases tend to grow as more data gets put in them. It's in their nature.
If you shrink the log is is going to have...
June 3, 2009 at 2:34 am
Viewing 15 posts - 38,716 through 38,730 (of 49,571 total)