Viewing 15 posts - 26,506 through 26,520 (of 59,099 total)
From your initial and follow-up descriptions, it looks like Scott's solution works. Are you all set now or do you still need some help?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2013 at 9:13 pm
TheSQLGuru (7/2/2013)
DannyCool (7/2/2013)
i am trying to automate sql 2012 installation and i dont want to install sql2012 and sp1 separately. I want it in 1 install file.
I am trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2013 at 5:09 pm
jw.lankhaar (6/13/2013)
For a limited number of rows (< 100) using a recursive common table expression is an alternative:
Please read the following article for why you should probably never use an...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2013 at 7:48 am
jasona.work (7/1/2013)
As in, one of the old hands stated where I'm sitting...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 7:33 pm
dwain.c (6/30/2013)
declare @t table
(
id int PRIMARY KEY,
PayCode char(2) null,
Amount decimal(15,2) null,
CDate date,
TranSeq int null
)
insert into @t
select 1, 'IR' ,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 7:20 pm
Sometimes splitting the backup to more than 1 file helps with performance a bit.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 7:17 pm
HanShi (7/1/2013)
You can use the -U and -P parameters. Take a look at http://msdn.microsoft.com/en-us/library/ms162802.aspx of the complete syntax.
If done correctly (ie, SQL Server is setup with Windows Authentication), you shouldn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 7:14 pm
I'll also suggest that you really shouldn't hard-code user name and password. Use a "trusted connection" instead. Use the -T parameter instead of -U and -P.
Also, you should...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 7:11 pm
lianvh 89542 (7/1/2013)
I ran a report on one of the SQL Server 2008R2 databases which identified an index as missing . I looked in the database and the index...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 6:47 pm
balamurugan.devadas (6/30/2013)
very intersting link,very useful for me.thanks a lot!
The next question would be... do you understand how all of those examples actually work? Your are, in fact, the one...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 6:31 pm
I have a unique method for handling such a thing. 😛 I tell the Devs when I'm going to do the refresh and that they have until then to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 6:22 pm
Why are we doing this in PowerShell?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 6:11 pm
I am curious a bit... how does this turn out to be an "EXEC xp_cmdshell error" like the title of this post suggests?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 6:08 pm
It'll be interesting what you do with last names like "van der waals" and first names like "Mary Jo" as well as people who have alphabet-soup after their last names...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 6:01 pm
Great Editorial. Now all we need is a link that teaches managers and developers how not to over-promise and one that teaches developers how to get over the "just...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2013 at 5:25 pm
Viewing 15 posts - 26,506 through 26,520 (of 59,099 total)