Viewing 15 posts - 36,256 through 36,270 (of 59,067 total)
Donalith (10/14/2010)
I'll look at the covering index though, that would be a good place to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 7:58 pm
sridharkannan7 (10/15/2010)
DetailsID FollowupID
1 0
2 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 7:50 pm
keymoo (10/19/2010)
Thanks very much for your help. Exactly what I needed.
Just make sure you follow the rules and add the safety check that Lutz wrote about. The code being...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 7:42 pm
mpalaparthi (10/18/2010)
I have a question.... I have 3 tables (table1, table 2 and table3)
table1: ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 7:35 pm
Hardy21 (10/21/2010)
I was thinking that due to multiple user is entering the data at same time, it may generate primary key violation.
Read up on it in Books Online... you'll feel...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 7:29 pm
mike 57299 (10/19/2010)
DECLARE @id int
DECLARE @result table(id id)
update generatepk
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 7:26 pm
If there's always two dashes, REVERSE (especially two reverses) is a bit expensive. This will work if there's always two dashes and be a bit faster.
DECLARE @FileName VARCHAR(50)
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 7:13 pm
AndrewSQLDBA (10/18/2010)
Thanks WildCatI figured it out right after another coffee.
I will keep your sample code for future queries.
Thanks again
Andrew SQLDBA
Two way street here, Andrew... can you please post what it...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 12:32 pm
SeanLange (10/21/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 12:31 pm
I'm not sure why everyone thinks this stuff has to be done in a single query. And, it probably should NOT be done in a single query. Create...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 12:24 pm
yitiana (9/19/2010)
Have you ever forgot or lost your SQL Server sa password?
I'm always amazed at how many people do such a thing.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 12:18 pm
Oksana March (10/24/2010)
I am not talking about what it *feels* like, but...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 12:15 pm
Wow... thanks for the insight on SSIS, folks. I've mostly resisted spending any decent amount of time on it because of what I've seen. Thanks to other people's...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 12:11 pm
As a side bar, IIRC, changing the recovery model to "Simple" breaks the restore chain. If this is transfer of data needs to occur on a regular basis, I'd...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2010 at 9:42 am
Paul,
Do the source (##temp) and destination (##Results) tables need to be global tables in order for the solution that you posted to work?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2010 at 8:41 am
Viewing 15 posts - 36,256 through 36,270 (of 59,067 total)