Viewing 15 posts - 2,236 through 2,250 (of 5,394 total)
It should not and I'm 99% sure it does not.
I don't have a reference to that, but you could easily find out comparing two installations.
December 19, 2011 at 3:24 pm
You should use non-breaking spaces instead of soft spaces.
Try replacing char(20) with "& nbsp;"
Hope this helps
Gianluca
Edited: remove the space between the "&" and "nbsp;". I had to post it like...
December 19, 2011 at 3:19 pm
I posted a corrected version of this code on my blog:
http://spaghettidba.com/2011/11/28/email-alert-dbcc-checkdb/
I hope you find it useful.
December 17, 2011 at 10:38 am
Koen Verbeeck (12/12/2011)
SQLRNNR (12/12/2011)
That would only be evidence if he became a MySQL, Firebird, NoSQL, PostGres, Informix or Oracle DBA.
Brrrr... Oracle.
I spent 4 hours yesterday setting up an Oracle client...
December 13, 2011 at 7:22 am
As Dave pointed out, EAV database design sucks in many ways. Fix it before you go crazy.
A possible way to mitigate the EAV pain is pivoting the attributes as deep...
December 12, 2011 at 2:50 am
BrainDonor (12/7/2011)
What kind of teacher would laugh at a six-year old's dream (at least to his face)?
December 7, 2011 at 3:14 am
ChrisM@Work (12/7/2011)
Most folks would recommend performing this degree of data massage in the presentation layer rather than the db.
That's good advice.
Another option could be a CLR function, which seems to...
December 7, 2011 at 3:12 am
If you want to record all the statements run by users, you have only one option, which is setting up a trace.
Be aware that it will likely slow down the...
December 7, 2011 at 3:10 am
Your issue doesn't seem to be related to the INSERT, but to the procedure call itslef.
Try using named parameters:
EXEC procedure @param1 = value1, @param2 = value2...
December 7, 2011 at 3:08 am
I would use a splitter function like this one:
http://www.sqlservercentral.com/articles/Tally+Table/72993/
You could split on " " and the split again on "=".
December 7, 2011 at 2:48 am
Sorry for the late reply. Glad you sorted it out.
December 5, 2011 at 2:29 pm
I suspect that you didn't change @sql to datatype nvarchar.
December 5, 2011 at 10:06 am
You can use sp_executesql:
ALTER Proc [dbo].[spGetStatisticByCategoryBLTimeLineConsultant](@Type varchar(50),@BL varchar(255), @TimeLine int, @Consultant int)
AS
DECLARE @param datetime
SET @param =
CASE
WHEN @timeline = 0 THEN DATEADD(yy,-100,getdate())
...
December 5, 2011 at 9:42 am
Dev (12/5/2011)
Gianluca Sartori (12/5/2011)
You could disable the constraints, check the data, delete invalid rows and enable the constraints again.
By disabling the constraint, you are allowing to enter bad...
December 5, 2011 at 8:29 am
Viewing 15 posts - 2,236 through 2,250 (of 5,394 total)