Viewing 15 posts - 2,086 through 2,100 (of 3,544 total)
or
STUFF('A1EC1XXXXXX-52',6,6,'')
if they are not really X's ![]()
Far away is close at hand in the images of elsewhere.
Anon.
November 16, 2005 at 6:21 am
REPLACE('A1EC1XXXXXX-52','X','')
Far away is close at hand in the images of elsewhere.
Anon.
November 16, 2005 at 6:19 am
Because '[Transaction]' is 13 chars long and the difference between the string with and without all '[Transaction]' is 26 (in this case) and divided by 13 gives 2 (the number of...
Far away is close at hand in the images of elsewhere.
Anon.
November 15, 2005 at 8:23 am
'The Dreaded Dynamic SQL Syndrome' ![]()
DECLARE @sql nvarchar(4000),@inStr nvarchar(2000)
SET @inStr = '[Transaction]=1000 OR [Transaction]=2000'
SET @sql...
Far away is close at hand in the images of elsewhere.
Anon.
November 15, 2005 at 7:20 am
Just had a thought, if max(i.jeno) + 1 is to be the same for all records then put this in a variable first and use the variable in the select
Far away is close at hand in the images of elsewhere.
Anon.
November 14, 2005 at 7:54 am
To use max(i.jeno) you must have a GROUP BY clause and you need to aggregate m.linecost or specify it in the GROUP BY
Far away is close at hand in the images of elsewhere.
Anon.
November 14, 2005 at 7:51 am
According to http://msdn2.microsoft.com/en-us/library/ms143393 only Enterprise to Enterprise upgrade is supported.
SQL Server 2005 Standard (and Enterprise) memory is limited to Operating system maximum and therefore, to be pedantic, not unlimited.
Far away is close at hand in the images of elsewhere.
Anon.
November 14, 2005 at 4:20 am
| Thanks for the kudo, David. It's a real pleasure to hear coming from you. |
We sycophants have got...
Far away is close at hand in the images of elsewhere.
Anon.
November 14, 2005 at 3:04 am
Not knowing how your system is setup but you could try something like this
DECLARE @sql varchar(8000)
SET @sql = null ' Need to do this at top of each loop
SELECT...
Far away is close at hand in the images of elsewhere.
Anon.
November 11, 2005 at 8:07 am
Very nice Jeff ![]()
Wish I'd thought of that ![]()
Could use your code for a COMPUTED COLUMN but...
Far away is close at hand in the images of elsewhere.
Anon.
November 11, 2005 at 7:50 am
Not sure I understand this ![]()
First, use IS NOT NULL instead of <> NULL
Second, is the column [Name] nvarchar or not ![]()
Far away is close at hand in the images of elsewhere.
Anon.
November 9, 2005 at 7:46 am
| My apologies for posting what I am about to post on here... |
EXEC(@querypart1 + @querypart2 + @querypart3 +...
Far away is close at hand in the images of elsewhere.
Anon.
November 9, 2005 at 7:31 am
| I am a clown. I make people laugh! I am a clown. I make people laugh! |
WOW ![]()
Far away is close at hand in the images of elsewhere.
Anon.
November 9, 2005 at 2:29 am
You could try using openrowset like this
SELECT * FROM
OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;HDR=YES;Database=C:\temp\book1.xls', [sheet1$])
but I have had problems using this if the spreadsheet does not reside on the sql server
Far away is close at hand in the images of elsewhere.
Anon.
November 8, 2005 at 8:38 am
Depending on how the new records are inserted
use a control record to store last key generated
CREATE TABLE ControlRec(key1 tinyint,key2 tinyint,key3 smallint)
INSERT INTO ControlRec(key1,key2,key3) VALUES (65,65,-1)
DECLARE @key1 tinyint,@key2 tinyint,@key3 smallint,@key char(5)
BEGIN...
Far away is close at hand in the images of elsewhere.
Anon.
November 8, 2005 at 8:11 am
Viewing 15 posts - 2,086 through 2,100 (of 3,544 total)