Viewing 15 posts - 361 through 375 (of 399 total)
Sean and ALZDBA - you guys are right. I think this is what I am going to do.
Also - what do you think about a select case statement, instead...
February 12, 2011 at 12:33 pm
Sean, it's not a situation that will ever see more than 1 record being updated at a time (this is on a smaller sized version of our PROD db. ...
February 11, 2011 at 9:42 am
I figured it out...It had to do with the way I was setting my local variable/parameter. I ended up setting them equal to the SELECT statement instead of the...
February 10, 2011 at 2:26 pm
Fixed it...One of my programmers noticed that the %Program Files (x86) was missing the additional '%'. I had previously tried that on some earlier code, but we also switched...
February 9, 2011 at 10:30 am
I guess I don't know how to format the filename after the WHERE statement. I've tried it in brackets, single quotes, and using another 'name' in the sys.sysaltfiles result...
February 9, 2011 at 10:13 am
Absolutely!
DECLARE @PATH VARCHAR(200)
IF EXISTS(SELECT * FROM sys.sysaltfiles WHERE [NAME] = 'master' LIKE '%Program Files (x86)')
SET @PATH = 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\'
ELSE
SET @PATH = 'C:\Program Files\Microsoft...
February 9, 2011 at 9:39 am
Quick additional note...
If I remark out the LIKE portion of the SELECT statement (and set the name to simply look for the 'master' entry - which the SELECT state will...
February 9, 2011 at 9:30 am
Mike - great specific question! No - that is where I am getting the error Incorrect syntax near the keyword 'LIKE'.
Any thoughts?
February 9, 2011 at 9:25 am
Thank you both very much for your time. I will work with your suggestions.
Mike - Thank you for that note below!
February 9, 2011 at 9:23 am
Mike / Sean -
Thank you both. I guess there is no way to simply remove the column constraint then without having to copy the column/table to a temptbl,...
February 9, 2011 at 9:16 am
Hi Mike -
This is definitely better than doing the whole table, but still - is there a way to simply remove the constraint from the column via T-SQL, as...
February 9, 2011 at 9:05 am
I still say that this will decision will haunt you or whoever made such a mandate very quickly. Any processes that insert data to any of these tables will be...
February 9, 2011 at 9:00 am
Correct - I simply need to remove the identity constraint from the column.
The customer requirement has changed, so needless to say, I am having to implement a very...
February 9, 2011 at 8:58 am
I'm removing the Identity Columns because I was asked to - not because I want to, nor because I think it would be a good practice. Trust me -...
February 9, 2011 at 8:48 am
I'm actually still having issues implementing this feature. I am getting errors where LIKE and ELSE are at. Not certain why though.
:ermm:
February 9, 2011 at 8:27 am
Viewing 15 posts - 361 through 375 (of 399 total)