Viewing 15 posts - 43,411 through 43,425 (of 59,063 total)
Cross post... please, no answers here. Go to the following instead...
http://www.sqlservercentral.com/Forums/Topic734177-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:53 pm
Jeffrey Williams (6/12/2009)
BTW - if you do not specify file locations in your create database statement, the default location defined for that instance will be used.
Voice of reason, right there.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:49 pm
Leave the first "-o" alone. Change all of the other "-o" to ">>".
Old DOS warrior trick. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:47 pm
This is a classic error that causes huge performance problems. The target of the update must also be included in the FROM clause if a join is present. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:45 pm
For the record, both Temp Tables and Table Variables start out in Memory and spool to TempDB if they get too big.
I suspect neither a Local Temp Table nor a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:38 pm
What helped it was that you got the COALESCE out of the WHERE clause.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:32 pm
anandhakrishnabca (6/12/2009)
I want to validate the given number. how to check for the following requirements in sql server 2005
1) how to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:25 pm
srikale (6/11/2009)
I want to insert a new column , check while inserting values.
For example : I have a table TBL with 2 columns , but...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:22 pm
I'm not sure why people think they need to do everything in a single query. Use the input parameters to get only the data you need from the properties...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 10:11 pm
Just in case...
[font="Courier New"] SELECT DATEADD(wk,DATEDIFF(wk,-2,'07/13/2008')+t.Number,-2)
FROM Master.dbo.spt_Values t
WHERE t.Type = 'P'
AND t.Number < DATEDIFF(wk,'07/13/2008','08/13/2008')+1
AND DATEADD(wk,DATEDIFF(wk,-2,'07/13/2008')+t.Number,-2) <= '08/13/2008'[/font]
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 9:49 pm
No... SQL Server 2000 doesn't have WITH/CTE. Instead, use a "Derived Table" which is nearly identical in most cases. A derived table is just like a CTE in that it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 9:39 pm
darryl (6/12/2009)
I am working on some sql to be used in a report. I have a transaction table called prtrxp. This table has about 100 fields....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 9:31 pm
Ok... problem solved... you think. A better question is, what are you using a cursor for?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 9:23 pm
I believe I'd tell the manager off. It's not his neck if data is inappropriately deleted... it's mine.
I would insist on moving the data to a subdirectory off the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 9:22 pm
If all you want is to calculate week days, there's a very short function at the following article.
http://www.sqlservercentral.com/articles/Advanced+Querying/calculatingworkdays/1660/
If you want work days instead of week days, I suggest...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2009 at 9:06 pm
Viewing 15 posts - 43,411 through 43,425 (of 59,063 total)