Viewing 15 posts - 196 through 210 (of 359 total)
ramadesai108 (6/28/2012)
I am using SQL Server 2008.
go to tools then options in there in the query options you can see what the character limit is 🙂
***The first step is always the hardest *******
June 28, 2012 at 4:20 pm
thanks guys i did try that already but still cant find the post i want 🙁 had a bit of code in it i wanted never mind thanks yous anyway...
***The first step is always the hardest *******
June 28, 2012 at 4:19 pm
It al depends on what your changing these values to, are your changes to the first 3 characters going to be the same for every row? if so then perhaps...
***The first step is always the hardest *******
June 28, 2012 at 8:24 am
I take it thats a no then :w00t: any moderators????
***The first step is always the hardest *******
June 28, 2012 at 8:19 am
If you only want the numerical value of said column then you could drop the character like for example.
providing the alphabetical character is the first character you could do somehting...
***The first step is always the hardest *******
June 28, 2012 at 2:46 am
@michael-2 Valentine Jones "max char 8192" this may be the case for SQL2000 but its not for SQL2012 wich i was using. I also used profiler trace to check...
***The first step is always the hardest *******
June 27, 2012 at 12:06 pm
i had the same issue with varchar(max) when using it to create dynamic SQL, when executing my SP i relieved syntax errors, i run the SP with select (@SQL) and...
***The first step is always the hardest *******
June 26, 2012 at 3:37 pm
can you provide some DDL please sample data etc
***The first step is always the hardest *******
June 19, 2012 at 3:39 pm
the reason you get duplicates is because of your joins are returning courtesan product, can you just explain how you want your results 🙂
***The first step is always the hardest *******
June 19, 2012 at 3:37 pm
arrr ok well i could only answer in what you put perhaps you can add some DDL to this thread representative data and what you expect the output to be,...
***The first step is always the hardest *******
June 19, 2012 at 9:43 am
Aye agreed
***The first step is always the hardest *******
June 19, 2012 at 9:27 am
@sean-2 Lange
It all depends on the task in hand, so in answer to this thread i gave some example SQL to help with his question, up to the user how...
***The first step is always the hardest *******
June 19, 2012 at 9:16 am
ahh sorry i misunderstood what you where trying to achieve
***The first step is always the hardest *******
June 19, 2012 at 8:39 am
i always use nolock 🙂
***The first step is always the hardest *******
June 19, 2012 at 8:38 am
Thanks Gila, not noticed that it wokred on size just noticed last tiem i restarted SQL server the report was empty
***The first step is always the hardest *******
June 19, 2012 at 7:59 am
Viewing 15 posts - 196 through 210 (of 359 total)