Viewing 13 posts - 136 through 149 (of 149 total)
For SQL 2005+, use the built in information schema views.
SELECT TABLE_CATALOG
, TABLE_SCHEMA
, TABLE_NAME
...
Wes
(A solid design is always preferable to a creative workaround)
July 17, 2013 at 1:11 pm
Assuming your indexes are appropriate for your query;
Create a view to pre-filter your data on the remote server. Ideally, create a single view that has all of the joins...
Wes
(A solid design is always preferable to a creative workaround)
June 18, 2013 at 11:32 am
You need to use the same collation for both sides of your comparison.
In your situation, one server ignores accent marks when comparing, the other includes accent marks in the comparison.
If...
Wes
(A solid design is always preferable to a creative workaround)
June 18, 2013 at 11:09 am
One other thing:
Please note that I have used TOP 100 PERCENT in the SELECT statement in this function because I want to retain the ORDER BY clause, which is otherwise...
Wes
(A solid design is always preferable to a creative workaround)
June 18, 2013 at 8:52 am
If "Show Actual Execution Plan" is set prior to executing the code and then both the queries (the CURSOR based one and the recursive CTE based one) are executed, you...
Wes
(A solid design is always preferable to a creative workaround)
June 18, 2013 at 8:47 am
Be aware the Print command will only display approximately 8000 characters of text.
Use the following script if you are scripting foreign keys for the entire database and need...
Wes
(A solid design is always preferable to a creative workaround)
April 8, 2013 at 9:05 am
--*********************************
--Show progress on the message tab
--*********************************
PRINT @sql
PRINT 'Column ' + CAST(@LoopNo AS NVARCHAR(5)) + ': ' +@Schema + '.' + @Table...
Wes
(A solid design is always preferable to a creative workaround)
November 7, 2012 at 4:14 pm
Glad to hear it.
I've already made a few minor revisions to it that I'll try to post a bit later when I have some time.
Wes
Wes
(A solid design is always preferable to a creative workaround)
November 7, 2012 at 10:11 am
@dwain.c
Excellent, that is just what I needed.
After working with it for a bit this morning, I've determined I need to assign the groups string in a checksum rather...
Wes
(A solid design is always preferable to a creative workaround)
October 16, 2012 at 10:06 am
I've used a slightly different approach for dynamic grouping. Instead of setting the grouping expression to a parameter, I define calculated fields in the dataset named simply Group#.
I have...
Wes
(A solid design is always preferable to a creative workaround)
October 11, 2012 at 9:31 am
DECLARE @ImportDate VARCHAR(8) = '10122012'
SELECT CAST(
RIGHT(@ImportDate , 4) + --Year
SUBSTRING(@ImportDate , 3 , 2) + --Month
LEFT(@ImportDate , 2) --Day
AS DATE)
Wes
(A solid design is always preferable to a creative workaround)
October 4, 2012 at 6:03 pm
@status is a report variable that determines if I need to filter by open date or resolved/closed date. @status is not contained in the cube.
Wes
(A solid design is always preferable to a creative workaround)
August 29, 2012 at 1:19 pm
Thanks for the reply. I'd prefer to remove them also, but I have to justify changing script that has been working in production without a problem.
How does NoLock affect...
Wes
(A solid design is always preferable to a creative workaround)
August 15, 2012 at 3:58 pm
Viewing 13 posts - 136 through 149 (of 149 total)