Viewing 15 posts - 196 through 210 (of 1,131 total)
There is a way to allocate specific CPUS to an application under SQL Server 2005 as explained on Slava Oks's blog at http://blogs.msdn.com/slavao/archive/2005/08/18/453354.aspx.
This week one of our customers had...
SQL = Scarcely Qualifies as a Language
June 16, 2009 at 9:57 am
The root cause is that for triggers, when the number of rows affected is significantly different that the prior execution of the trigger, SQL Server automatically creates a new execution...
SQL = Scarcely Qualifies as a Language
June 16, 2009 at 9:24 am
Aaron & Paul White:
I tried out Paul alternative solution by changing my posted trigger Revision2.PurchasesLatest_tau
Carl's code
FROMdeleted AS Old
INNER LOOP JOIN
Revision2.PurchasesLatest Cur -- WITH (FORCESEEK)
ON Old.ProductTypeID = Cur.ProductTypeID
;
Changed to
FROMdeleted AS...
SQL = Scarcely Qualifies as a Language
June 16, 2009 at 7:17 am
There are some performance comparisons of various techniques at http://weblogs.sqlteam.com/peterl/archive/2009/06/12/Timings-of-different-techniques-for-finding-missing-records.aspx
"NOT EXISTS" was the fastest for those specific test conditions.
SQL = Scarcely Qualifies as a Language
June 15, 2009 at 7:53 pm
Found a solution that allows multiple connections to be updating the same table, but of course, different rows without blocking occurring.
The solutions is to include the following two states:
1) ...
SQL = Scarcely Qualifies as a Language
June 15, 2009 at 5:49 pm
Dave Portas , SQL Server MVP, has a solution for this type of problem that has been published in Joe Celko's "SQL For Smarties" in Chapter 24.
CREATE TABLE Runs
(seq_nbr...
SQL = Scarcely Qualifies as a Language
June 14, 2009 at 3:03 pm
Paul White has posted his understanding of the problem and I am also waiting for confirmation or revision. I have these additional questions:
Are the provided table definition for the...
SQL = Scarcely Qualifies as a Language
June 14, 2009 at 7:11 am
Aaron (6/13/2009)PS: Why go through all of the trouble creating this code and formatting it if it's just going to get hosed. I attached a text file with the formatting...
SQL = Scarcely Qualifies as a Language
June 13, 2009 at 7:56 pm
After applying SQL Server 2000 SP4, did you apply the AWE HotFix ?
http://support.microsoft.com/kb/899761
SQL = Scarcely Qualifies as a Language
June 12, 2009 at 2:54 pm
What you are requesting, a filtered index, is available under SQL Server 2008 but not under 2005
The 2008 syntax for a filtered index would be:
CREATE UNIQUE NONCLUSTERED INDEX...
SQL = Scarcely Qualifies as a Language
June 12, 2009 at 8:53 am
For a user, SSMS will only list those objects where there is some privilege on that object.
Recommend is to create a database role, grant/deny privileges to the database...
SQL = Scarcely Qualifies as a Language
June 11, 2009 at 9:20 am
There is script in the SSC library titled "Delete old versions of DTS packages" which should solve your problem.. You can add the stored procedure and then have the...
SQL = Scarcely Qualifies as a Language
June 11, 2009 at 8:30 am
Ken McKelvey's solution is much more elegant than mine. Ken's solution accesses the table once, compared to my solution, which accesses the table 3 times.
Very nice...
SQL = Scarcely Qualifies as a Language
June 11, 2009 at 7:58 am
Here are two solutions, both of which are complicated because:
A) the table is denormalized as the BasePrices are an array with the column name indicating the month of the...
SQL = Scarcely Qualifies as a Language
June 11, 2009 at 5:05 am
IP address will work but you must reference a share on the remote server and the SQL Server service account must have access to that share. Each partitions has...
SQL = Scarcely Qualifies as a Language
June 10, 2009 at 11:14 am
Viewing 15 posts - 196 through 210 (of 1,131 total)