Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Do Not Call list Expand / Collapse
Author
Message
Posted Wednesday, April 3, 2013 3:34 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 9:50 PM
Points: 23,045, Visits: 31,570
And what happens if you make the phone number field varchar(8)?



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1438601
Posted Wednesday, April 3, 2013 3:43 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 11:57 AM
Points: 388, Visits: 1,527
Lynn Pettis (4/3/2013)
And what happens if you make the phone number field varchar(8)?


Heh. Curiously, I can use Python to split the file up (opening the whole file with any of the programs I have available is impossible; the computer comes to a screeching halt), and the split files seem to agree with the \ n row terminator. Maybe I'll try using it to re-save the whole thing to one file?

When I use any length short of nvarchar(max), I get the truncation error I posted before, up to and including varchar(8000).
Post #1438604
Posted Wednesday, April 3, 2013 3:51 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 9:50 PM
Points: 23,045, Visits: 31,570
erikd (4/3/2013)
Lynn Pettis (4/3/2013)
And what happens if you make the phone number field varchar(8)?


Heh. Curiously, I can use Python to split the file up (opening the whole file with any of the programs I have available is impossible; the computer comes to a screeching halt), and the split files seem to agree with the \ n row terminator. Maybe I'll try using it to re-save the whole thing to one file?

When I use any length short of nvarchar(max), I get the truncation error I posted before, up to and including varchar(8000).

Worth a shot.



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1438605
Posted Wednesday, April 3, 2013 4:06 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 11:57 AM
Points: 388, Visits: 1,527
Lynn Pettis (4/3/2013)
erikd (4/3/2013)
Lynn Pettis (4/3/2013)
And what happens if you make the phone number field varchar(8)?


Heh. Curiously, I can use Python to split the file up (opening the whole file with any of the programs I have available is impossible; the computer comes to a screeching halt), and the split files seem to agree with the \ n row terminator. Maybe I'll try using it to re-save the whole thing to one file?

When I use any length short of nvarchar(max), I get the truncation error I posted before, up to and including varchar(8000).

Worth a shot.


Yep, working. Thanks for your gender neutral time.

Some days SQL makes me want to go put together Ikea furniture to relax. Sheesh.

Post #1438608
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse