Viewing 15 posts - 2,101 through 2,115 (of 3,232 total)
Can you post some sample data for each table and the results you are expecting to get?
September 17, 2007 at 12:55 pm
First, you'll need to be able to define the rules surrounding the split. One can look at your string and your output table and guess, but it sure helps, especially...
September 13, 2007 at 10:09 am
It may also help to look and see if there is a DELETE trigger on the table you are deleting from or an INSERT trigger on the insert table.
September 12, 2007 at 9:27 am
This is normal behavior as the trigger is part of the UPDATE transaction to that row. SQL Server holds the locks that were placed on the row for the UPDATE...
September 12, 2007 at 8:54 am
I would not consider partitioning a tuning technique. What did the article say about partitioning that you have questions on.
September 11, 2007 at 4:13 pm
Read up on Locking Hints in BOL. Yes, you can help with performance by using locking hints to tell SQL Server to use a specific type of lock. Using locking...
September 11, 2007 at 4:11 pm
I didn't think Aaron was being negative. It sounds like a perceptive observation to me. Look up EXEC in BOL. You need to build your ALTER TABLE statement into a...
September 11, 2007 at 3:42 pm
You mentioned that you noticed a bit of the self-blocking during production hours. How did you identify the self-blocking to begin with? Was your production system experiencing slowness that you...
September 11, 2007 at 9:28 am
Yes, I second what Vladan posted. Read through BOL on not only that topic but on transactions in general and post any questions you come accross. The default behavior for...
September 11, 2007 at 7:47 am
You've either specified a BEGIN TRANSACTION without doing a COMMIT/ROLLBACK, or you have SET IMPLICIT_TRANSACTIONS set to ON.
September 10, 2007 at 1:02 pm
Can you specify an article that states this? What is the articles position on this? I would say that it depends on what you are attempting to aggregate and whether...
September 10, 2007 at 12:59 pm
Self blocks are usually due to long I/O wait times. You've obviously been able to capture the self blocking. Run sp_lock the next time you see the self blocking and...
September 10, 2007 at 12:57 pm
Just add a 'SELECT * FROM #TempTable' where you need to view the data. There is no need to use the PRINT statement to view the data.
September 7, 2007 at 11:13 am
As far as #1 goes, when performance tuning a query, logical and physical reads can be viewed by using SET STATISTICS IO ON. Physical reads represent how many pages SQL Server...
August 31, 2007 at 11:58 am
Not quite. They backup file that you have is a SQL Server backup. The physical file names you see in the options tab are the physical Data and Log file...
August 30, 2007 at 4:13 pm
Viewing 15 posts - 2,101 through 2,115 (of 3,232 total)