Viewing 15 posts - 37,501 through 37,515 (of 59,098 total)
Actually, I do have another question...
You seem to have very neatly solved the problem in the .xls file. Your goal is (in your words) to chart the output. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 8:09 pm
First of all, very well done on the data and the loader code you provided. You just can't ask for much better than that.
My only questions would be...
1. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 8:00 pm
NewBeeSQL (7/25/2010)
No luck with your code..can you please generate the code which was mentioned in my first mail with your logic...
This is one of those places where a cursor isn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 12:45 pm
Adiga (7/25/2010)
You can create a stored procedure for this code and use sp_MSforeachdb to execute it against each database.Example:
EXEC SP_MSFOREACHDB @COMMAND1 ='SELECT DB_NAME(),DATABASEPROPERTYEX([?],'IsAutoClose''
That doesn't actually avoid a cursor. MSForEachDB...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 12:44 pm
Tara-1044200 (7/26/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 11:44 am
GilaMonster (7/26/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 11:36 am
8000 characters has never been a limit for code. ie... EXEC (@a+@b+@c.... etc).
What are you using to import your data with because there's no 8k limit on imports either....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 11:34 am
Michael Valentine Jones (7/26/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 11:24 am
J-F Bergeron (7/26/2010)
Ken@Work (7/26/2010)
The RowNumber() approach looks nice.Is that a Server 7 command? I'm having trouble with it.
Sadly, no, it's a sql server 2005 function. Sorry to have mislead...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 11:21 am
Eugene Elutin (7/26/2010)
Jeff Moden (7/26/2010)
asiaindian (7/26/2010)
Add a month to the startdatedeclare @StartDate date
set @StartDate = '01-31-2010''
select DATEADD(mm, 1, @StartDate)
Repeat above code through any number of frequencies. Hope this helps.
Ok.... you...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 11:13 am
asiaindian (7/26/2010)
Add a month to the startdatedeclare @StartDate date
set @StartDate = '01-31-2010''
select DATEADD(mm, 1, @StartDate)
Repeat above code through any number of frequencies. Hope this helps.
Ok.... you have 100 frequencies... now...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 7:38 am
Gianluca Sartori (7/26/2010)
Jeff Moden (7/26/2010)
Gianluca Sartori (7/26/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 6:42 am
jprabha.d (7/24/2010)
Thanks For the Solution i used Running value Function that is in SSRS,
A wise choice... how is it in the area of performance?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 6:37 am
Gianluca Sartori (7/26/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 6:34 am
cmapowers (7/25/2010)
This seems to be a correlated sub-query. Does this apply to non correlated sub-query?
All non correlated sub-queries break down to being an inline view whether they're in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2010 at 6:32 am
Viewing 15 posts - 37,501 through 37,515 (of 59,098 total)