Viewing 15 posts - 25,486 through 25,500 (of 59,099 total)
SQLKnowItAll (11/4/2013)
Future Plan: Move all images out of the database to an smb file share and only store the path within the database.
I used to think that was the best...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 5:53 pm
erikd (11/4/2013)
I was reading through, and got sort of confused about the 23rd point:
If you need to insert many rows at once into a table,
use, where possible, the multi-row VALUES...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 5:21 pm
Lee Hopkins (11/4/2013)
Separate audit table for each of the tables would at this time not...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 5:10 pm
Kurt W. Zimmerman (11/4/2013)
Jeff Moden (11/4/2013)
mick burden (11/4/2013)
thanks Jeff, it's not something I've used before. What is the advantage? and can the table created be read using VB.net?
The biggest advantage...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 11:37 am
mick burden (11/4/2013)
thanks Jeff, it's not something I've used before. What is the advantage? and can the table created be read using VB.net?
The biggest advantage is that you can use...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 11:20 am
Sqlsavy (11/4/2013)
Is it possible to delete old backups using SQL backup script with RETAINDAYS ?
No and apologies for the confusion on that.
Normally when I see folks with a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 10:38 am
SQLSteve (10/23/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 8:15 am
While not huge, 53 million rows isn't exactly a small table. While it certainly could be parameter sniffing, it could also be that the data was driven out of...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 8:10 am
How many rows will this table eventually have and how often will it need to take new inserts or updates?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 8:07 am
jsteinbeck-618119 (11/4/2013)
Ah, the Table-Valued Functions... yes, I can do that...
Table Valued Functions aren't the same as CLR. CLR, specifically SQLCLR, is code written in another language (such as C#)...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 8:05 am
It would probably make your whole life a lot easier if you changed the stored procedure to an iTVF (inline Table Valued Function) because then you could easily create a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 7:56 am
wendy elizabeth (11/1/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2013 at 7:37 am
The test data that you posted on SQLFiddle has some serious problems with wrapped lines and missing quotes.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2013 at 6:35 am
As "Yoggi" used to say, "When you come to a fork in the road, take it." 😀
In other words, why not learn to do both?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2013 at 5:31 am
SELECT DATEADD(mm,DATEDIFF(mm,0,somedatetimeexpression),0)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2013 at 10:01 pm
Viewing 15 posts - 25,486 through 25,500 (of 59,099 total)