Viewing 15 posts - 181 through 195 (of 197 total)
I just made it through the last of the sub-prime melt down in Southern California. At our peak, we had 9 DBA's on staff, 4 focused on production, and 5...
October 7, 2009 at 4:45 pm
You've definitely got different versions of the database instance patched, one to SP2 with a hot fix and the other to SP3. Have you tried failing over to the SP2...
October 7, 2009 at 9:19 am
If you place the select and update from the control table in a separate transaction (let's say it returns 1001 and updates the next value to 1002) and commit that...
October 6, 2009 at 5:09 pm
It sounds like your control table is a bottleneck in the application design as each connection has to wait for the previous select and update to complete before it can...
October 6, 2009 at 4:05 pm
Ok, it looks like I need more information to assist with this. What clustering solution are you using? In Windows clustering, patching the database instance should patch all of the...
October 6, 2009 at 2:54 pm
You need to patch the client tools on the other node. When you run SP3, it patches the database engine and the client tools on the node that you run...
October 6, 2009 at 2:23 pm
I ran into the same issue on a Windows clustered environment. When you apply SP3, it patches the database engine and the client tools for whatever node that you're running...
October 6, 2009 at 2:19 pm
I've always made it a practice to separate table and index data into separate filegroups and therefore separate files. After all, isn't that the only way you can place a...
October 2, 2009 at 10:11 pm
You should be able to use the EMPTYFILE clause of the DBCC SHRINKFILE command to move the contents of the second file into the first file. Once that's done, you...
October 2, 2009 at 9:19 pm
I've never found a good online solution and always shut down the SQL server and run the disk defrag utility. As already stated, configure a reasonable autogrowth setting based on...
October 2, 2009 at 9:12 pm
Refer to this white paper: http://technet.microsoft.com/en-us/library/cc966545.aspx
Essentially, you never want to enable auto shrink but use auto-grow as an emergency just in case. You should try to configure tempdb...
October 2, 2009 at 8:48 pm
Your best bet is to use an existing index rebuild script that checks the fragmentation levels of the indexes and only rebuilds ones that are fragmented more than a specific...
June 25, 2009 at 10:03 am
I believe you need to create the new schema and then transfer the object ownership of all existings objects to it. You can look up ALTER SCHEMA in books on...
June 24, 2009 at 4:07 pm
There's not a lot of detail in your problem description, but you should probably look at configuring some replication alerts to notify you whenever a failure occurs.
The following links might...
June 24, 2009 at 4:02 pm
You can run this, but it will only tell you the current owner of the job, not who created it. If that person authenticated with Windows credentials when creating it,...
June 24, 2009 at 3:47 pm
Viewing 15 posts - 181 through 195 (of 197 total)