Viewing 15 posts - 48,751 through 48,765 (of 59,102 total)
I'm thinking it could help employers notice me if they see who I've had forum discussions with.
Heh... WHICH forum discussions would you be talking about? You have precisely 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 4:20 pm
Which edition of SQL Server 2005 are you trying to install?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 4:12 pm
Venkatesan Prabu (8/17/2008)
insert into FirstTable values('Doc1','Attrib1','val1')
insert into FirstTable values('Doc2','Attrib2','val2')
insert into FirstTable values('Doc3','Attrib3','val3')
insert into FirstTable values('Doc4','Attrib4','val4')
select * from FirstTable
create table SecondTable(Attrib2 varchar(10),Attrib22 varchar(10))
insert into SecondTable...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 3:49 pm
GilaMonster (8/17/2008)
FirstTable has 1 lakh record , Second table has 2 Lakh record and Third...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 3:35 pm
Please post the link where you found the pricing so we can figure out what you mean by the "OEM" version because, to the best of my knowledge, nothing is...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 3:33 pm
masood24 (8/17/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2008 at 3:27 pm
Heh... that's known as a "Headerless Ragged Right" file and they're a bugger to import correctly. BCP and BULK insert require that all the rows have the same number...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 8:47 pm
No.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 8:01 pm
Jeffrey Williams (8/16/2008)
Oops - forgot the temp table, thanks Jeff.
No problem... it's the beauty of a forum... world's biggest team. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 8:00 pm
You CAN have file names with spaces (although, I prefer not to). And, you can easily run commands on those file names by enclosing the filename in double quotes......
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 7:57 pm
What the heck is the matter with using Replication?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 3:53 pm
And, yes, it's easy to dump that into a temp table...
Yes, this can be done using an alias. Example:
SELECT t1.col1 AS t1_col1,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 3:51 pm
Considering that the drive to work is 112 miles round trip, I'd love to see my company implement that right the heck now! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 3:46 pm
bitbucket (8/16/2008)
Update Dbo.Table1 UPDATE dbo.location SET local_Phone = '91'+local_phone
Just to be sure, I'd add a check to make sure the numbers haven't already been updated...
UPDATE dbo.Table1
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 3:42 pm
Joe Torre (8/16/2008)
It is often faster to create a temp table yourself to replace the sub-select
Being a bit of a skeptic, let's see the test you did that proves that....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2008 at 3:35 pm
Viewing 15 posts - 48,751 through 48,765 (of 59,102 total)