Viewing 15 posts - 31 through 45 (of 595 total)
Sorry, I don't use Perl, so I can't really help with that. I assume you've already searched for help on this, but here are some that seemed helpful.
http://perl.active-venture.com/pod/perlguts-unicode.html
April 2, 2007 at 11:14 am
Did you develop the application, or did you purchase it? I'm pretty sure that the error is a .NET error and not SQL Server.
April 2, 2007 at 7:47 am
It appears that the lower case alpha character is only supported in Unicode. Look at this example (The SET statements have the correct alpha, just in case posting this converted...
April 2, 2007 at 7:41 am
If [id] is the primary key for table B, then it is not possible to have a NULL [id]. Please post actual CREATE TABLE statements.
April 2, 2007 at 7:29 am
Look over this example. This allows multiple null values for the varchar column nulltest, but each non-null must be unique.
CREATE TABLE NullPKTest
(
nid int PRIMARY KEY
, nulltest...
March 23, 2007 at 6:35 am
Firstly, let me say that I don't have any 64-bit systems. In re-reading the first link [ http://www.microsoft.com/downloads/details.aspx?familyid=220549b5-0b07-4448-8848-dcc397514b41&displaylang=en ] I realized that there is no 64-bit version of SQL Server Express,...
March 16, 2007 at 5:57 am
The 36.5 MB file contains only the 32-bit version. The 53.5 MB file contains both the 32-bit and the 64-bit versions.
March 15, 2007 at 11:14 am
If you have a function that converts int/binary to a hex string (type varchar), such the one shown below, you could do this to return a string representation of the...
March 15, 2007 at 10:55 am
Does the string representation need to be hex? If decimal is ok, look at this example:
DECLARE @bin binary(8)
SET @bin = 0x7FFFFFFFFFFFFFFF
SELECT @bin AS binaryValue
...
March 15, 2007 at 10:45 am
The value you are trying to insert for column DOWN_TRAFFIC is way too big. DOWN_TRAFFIC is declared as numeric(10,0) and the value you are inserting is 16 digits ( 9702545870094336...
March 13, 2007 at 12:03 pm
Ronald was correct - your SELECT statement is too big. You are joining 12 or 13 tables (I lost count!), and the total size of all columns selected is too...
March 13, 2007 at 10:59 am
Can you post the actual CREATE TABLE statement? The one you posted is invalid. All of the column names are the same, and the last column is missing a closing...
March 13, 2007 at 6:54 am
For many errors, SQL Server will continue executing code. It would be up to you to trap certain conditions and then STOP processing. There is no way to cause SQL...
March 12, 2007 at 7:48 am
When your language setting is us_english, SQL Server accepts dates in two formats: MDY and YMD. YMD is a "universal" format which accepted regardless of the language setting. That...
March 12, 2007 at 7:07 am
This is a cross-post. Continue here: http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=350095
March 9, 2007 at 9:17 am
Viewing 15 posts - 31 through 45 (of 595 total)