Viewing 15 posts - 511 through 525 (of 5,356 total)
Thanks for posting the results. Good to see it is finally solved somehow.
Would you mind posting some of your SAN specs?
April 19, 2005 at 1:31 pm
Will this help?
DECLARE @stmt NVARCHAR(1000)
SET @stmt = 'USE NORTHWIND' + CHAR(10)+'SELECT * FROM Orders'
EXEC sp_executeSQL @stmt
April 19, 2005 at 1:26 pm
That's the way it is. You can't select your favorite fora. Before this forum package, Snitz was used here. And it might be just me, but Snitz was better and...
April 19, 2005 at 1:13 pm
Expected behaviour. Quoting from BOL (CAST and CONVERT):
When converting character or binary expressions (char, nchar, nvarchar, varchar, binary, or varbinary) to an expression of a different data type, data can...
April 19, 2005 at 12:43 pm
Interestingly, you need to look at IDENT_CURRENT in BOL to see why SCOPE_IDENTITY() is preferable to @@IDENTITY
April 19, 2005 at 12:28 pm
Very few things happen "out of nowhere". Any changes to app or db recently? Any entry in log files? Did you run DBCC CHECKALLOC, DBCC CHECKCATALOG or DBCC CHECKTABLE?
Which tool...
April 19, 2005 at 12:25 pm
Igor,
I haven't looked at it, but I don't question the quality of your code. All I wanted to say is, that 1 post in the right forum is all that...
April 19, 2005 at 12:19 pm
Wow, certainly more than enough
How should the output look like?
April 19, 2005 at 8:20 am
Sorry, but I think this is exactly what I have posted, or? The table GUID_T has a VARCHAR(50) for the GUID. The table GUID_NEW has the UNiQUEIDENTIFIER data type. When...
April 19, 2005 at 7:57 am
Now, this looks completely different now. An interesting, yet important part of your problem you didn't conceal here in this thread, don't you think?
April 19, 2005 at 7:54 am
Am I understanding you right?
SET NOCOUNT ON
CREATE TABLE GUID_T
(
guid VARCHAR(50) DEFAULT NEWID() PRIMARY KEY
, col1 VARCHAR(30)
)
CREATE TABLE GUID_NEW
(
guid UNIQUEIDENTIFIER DEFAULT NEWID() PRIMARY KEY
, col1 VARCHAR(30)
)
INSERT INTO...
April 19, 2005 at 7:47 am
You should get into the habit, using a considered safe date format like SQL Server's style 112 or 126 to avoid such kind of problems.
See if these help explaining
April 19, 2005 at 7:36 am
...cause if you're not specifying the columns of the insert you can have a lot of problems
Even more problems than the use of a cursor will cause?
What about getting rid...
April 19, 2005 at 6:55 am
Not sure if I understand you correctly, but wouldn't a FULL OUTER JOIN on Streetcode do the job?
If not, please post your desired output. DDL and sample data to play...
April 19, 2005 at 6:52 am
Viewing 15 posts - 511 through 525 (of 5,356 total)