Viewing 15 posts - 76 through 90 (of 172 total)
I just wanted to add that we had tried using NAS in the past and we were disappointed but things have changed. Because of the changes, we are in the...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
September 2, 2005 at 7:59 am
Thanks guys. As my post said, about half-way through, I thought this was the case but I just needed clarification.
Thanks again,
hawg
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
September 2, 2005 at 7:09 am
Another option would be to build a table to hold the values for your parameter values and use that table in your procedure. This method could help you avoid a...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
August 16, 2005 at 9:17 am
Sorry guys, two things. One, the server I did this on earlier was also EE. Extra memory cannot be used with Standard Edition.
Also, I won't be applying SP4 yet.
Thanks,
hawg
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
August 10, 2005 at 1:23 pm
Just wanted to mention that you might want to try the Free SQL Server Add-on Tool called SQL Digger (http://sqldigger.bdsweb.be/). This tool is great and easy to use. You...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
August 4, 2005 at 10:10 am
Thanks for the help. I actually ended up building a UDF to handle this because we have this scenario many times in our development. In many of the apps we...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
July 28, 2005 at 3:36 pm
My apologies, I may not have made my example clear.
Assume this is my procedure:
CREATE PROC usp_CheckList(
@parm varchar(100))
AS
SELECT *
FROM dbo.MyTable
WHERE checkfield IN (@parm)
GO
The value I am passing into the procedure is:
'ABC','XYZ','JKL'
Is there...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
July 28, 2005 at 9:42 am
Thanks for the insight. I had just never seen this before and I was curious. Everything makes sense.
Thanks again,
hawg
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
July 21, 2005 at 7:07 am
You wrote:
NAS or SAN
Microsoft does not recommend the use of NAS for the performance problems you've cited. If you have the option, go with the NAS or a dedicated...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
July 12, 2005 at 2:36 pm
This is just taking a shot based on what you gave and without the DDL but give the following a try. If it doesn't work, we really need to see...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
July 7, 2005 at 8:56 am
Expanding on David's solution, if you wanted to, you could remove the leading zeroes but keep spaces for these zeroes using the following:
REPLICATE(' ', PATINDEX('%[^0]%', [Name]) - 1) + SUBSTRING([name],PATINDEX('%[^0]%',[Name]),LEN([Name]))
Not...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
July 5, 2005 at 2:42 pm
Rob's answer still works only with changing the "C" sort from desc to asc like the following:
select * from #tbl t
where t.i =
(
select top 1 t1.i FROM #tbl t1
where...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
May 23, 2005 at 12:00 pm
Calm down Joe before you blow a gasket.
I've never claimed to be a complete SQL expert and this was just a quick example. Regardless of what the definition is...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
May 23, 2005 at 10:21 am
I will agree that it is best to build your database where there is a logical PK but I have had multiple instances where I simply needed a unique ID...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
May 23, 2005 at 10:05 am
Rob's answer is the best with one exception, you will need to make the sort for "c" to be ascending instead of descending.
Joe, I'm curious why you said you never...
----------------------------------------------------------01010011010100010100110000100000010100110110010101110010011101100110010101110010001000000101001001101111011000110110101101110011
May 23, 2005 at 8:03 am
Viewing 15 posts - 76 through 90 (of 172 total)