If @PkTable, @PKSchema (provide if not dbo), or @PkColumn are not existing values, the proc will return no results.

4x RAM is more than plenty. I think most machines get unstable when they start using more than 2x and machines with adequate ram will never hit 2x RAM on...

I use the /PAE boot.ini switch on a 32-bit windows XP workstation with 4GB of RAM. It not only lets me use 3.25GB of that RAM, it lets me...

Only works on SQL 2005. Also Check the compatibility level of the database.

Put up a new version (it'll get moderator-approved sometime monday). Still same the brute-force method, but hard-coded checks up to the first full data page of the table of...

I just uploaded a new version

I got the fastest method in http://sqlblog.com/blogs/hugo_kornelis/archive/2006/09/23/Prime-numbers.aspx beat! Gotta give this blogger credit though because I'm using his idea of using modulo to eliminate the...

The schema are in the main snapshotter scripts. This is only some sample reporting procs. The snapshotter procs (Util_BuildSpaceLog) have the DDL and data gathering DML. Look in...

This just peeks into the dynamic management views and does the joins for you, possibly replaces the comma delimiters with another of you chossing (if you pick something other than...

Look under 'Related content'

See all my scripts at http://www.sqlservercentral.com/Authors/Scripts/Jesse_Roberge/13538/

Yeah if you could restrict the rows (and columns if savings is alot) it would be more reasonable. None of your code had WHERE clauses so I assumed...

Makes sense now. I would still suggest that if the running totals requirement was the dominant form of querying on the table, I would rather just un-partition the whole...

I don't get this. Both of the solutions create a non-partitioned instance of the partitioned table. One form is a temp table, and the other form is a...

All my stuff is 2005-only (most work on 2008 also) unless documented to say it works on SQL 2000 (the delimiter functions and the 2000 version of the counter /...

Works on SQL 2005 only. The build would be 9.xxx.xxx

I would do (FranchiseID, AppointmentTypeID, ApptDateTime) INCLUDE (CustomerID)

This is because only one inequality column ( =,<=, IN(), BETWEEN) can be range-scanned. If you wanted to follow BOL documentation for...