Viewing 15 posts - 25,471 through 25,485 (of 59,099 total)
Heh... I had to think about it. For me, the correct answer would have started with "Exec xp_CmdShell". 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 2:04 pm
Phil Parkin (11/5/2013)
Dwain does it again - nice article sir!
Ditto that! Nicely done, Dwain. Great explanations and revelation of code.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 11:46 am
jsteinbeck-618119 (11/5/2013)
The user is in the DB via GUI, they click a button on the form the basically says, "Lets look at new faxes that came in", and this form...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 7:41 am
dwain.c (11/5/2013)
Jeff Moden (11/5/2013)
dwain.c (11/5/2013)
For what it's worth, I'm in favor of a selective culling of the gene pool. 😛
I assure you, it's just words from some serious pent up...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 1:22 am
SQLRNNR (11/4/2013)
Ed Wagner (11/4/2013)
SQLRNNR (11/4/2013)
jasona.work (11/4/2013)
Trying to get in touch with the people who need to update the application, people...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 1:08 am
dwain.c (11/5/2013)
For what it's worth, I'm in favor of a selective culling of the gene pool. 😛
I assure you, it's just words from some serious pent up frustration from working...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 1:01 am
I guess I'm a little confused about your process. What do you mean by "when a user access this file from within the DB"?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 12:58 am
dwain.c (11/4/2013)
Sounds like you have the luxury of an orderly, controlled shop. Congratulations for exercising such strict controls (and being able to)!
I don't think of them as strict controls...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 12:39 am
hoseam (11/4/2013)
Jeff Moden (11/4/2013)
How many rows will this table eventually have and how often will it need to take new inserts or updates?
1. As many as it could
2. Not very...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 12:18 am
GilaMonster (11/4/2013)
Jeff Moden (11/4/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2013 at 12:03 am
dwain.c (11/4/2013)
Jeff Moden (11/4/2013)
shashianireddy (11/4/2013)
sql 2008 version ,,nvarchar(MAX)
You're using NVARCHAR(MAX) for a housenumber???? In SQL Server 2008???? Why?????
You probably don't release it but you cannot rebuild a clustered index...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 11:09 pm
shashianireddy (11/4/2013)
Iam try this quarie but not display above format show as above
For the given data, it certainly does. Please post the data you're using where it doesn't.
Declare @tblTemp...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 10:55 pm
shashianireddy (11/4/2013)
sql 2008 version ,,nvarchar(MAX)
You're using NVARCHAR(MAX) for a housenumber???? In SQL Server 2008???? Why?????
You probably don't realize it but you cannot rebuild a clustered index in an Online...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 10:42 pm
twin.devil (11/4/2013)
Better practice is to maintain a sequence column in the table.
Why? I've added such a thing only when there is no other means and there is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 10:33 pm
SQLTestUser (11/4/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2013 at 9:16 pm
Viewing 15 posts - 25,471 through 25,485 (of 59,099 total)