[MS SQL Server] Bulk Insert text file into SQL table |
- Bulk Insert text file into SQL table
- Repair instance
- how to script out create table script of all tables in a database
- SQL Server SSIS Packaage Error Code 1073741819.
- need to get the all jobs information
- Page file best practices and memory upgrade.
| Bulk Insert text file into SQL table Posted: 06 Aug 2013 02:54 AM PDT Hi,I have a requirement to load sql server table from text file using the below command....and the file is in the local server....its throwing an error...could someone help me on this please....it urgent...BULK INSERT dbatest.dbo.test FROM 'L:\test.log' WITH (FIELDTERMINATOR = ',',ROWTERMINATOR = \r')Error :Msg 4866, Level 16, State 1, Line 1The bulk load failed. The column is too long in the data file for row 1, column 1. Verify that the field terminator and row terminator are specified correctly.Msg 7399, Level 16, State 1, Line 1The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.Msg 7330, Level 16, State 2, Line 1Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".Thanks in advance... |
| Posted: 05 Aug 2013 10:21 PM PDT Hi Experts,What exactly happens when we try to repair the instance using the REPAIR option under maintenance in Installation.Thanks in Advance |
| how to script out create table script of all tables in a database Posted: 06 Aug 2013 12:52 AM PDT I would like to script out all create table script in a database and save it in a table. How to perform this operation? |
| SQL Server SSIS Packaage Error Code 1073741819. Posted: 05 Aug 2013 11:33 PM PDT Dear All,We have faced the following Error Recently in SSIS Package Scheduling.Error Code :The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.Detailed Error List :Date 06/08/2013 10:02:25Log Windows NT (Application)Source Application ErrorCategory Application Crashing EventsEvent 1000Computer MessageFaulting application name: dtexec.exe, version: 2009.100.1600.1, time stamp: 0x4bb679aaFaulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82Exception code: 0xc0000374Fault offset: 0x000da94fFaulting process id: 0x3a78Faulting application start time: 0x01ce925df1afd4c7Faulting application path: D:\Program Files (x86)\Microsoft SQL Server\100\DTS\binn\dtexec.exeFaulting module path: C:\Windows\SYSTEM32tdll.dllReport Id: 313df978-fe51-11e2-93ff-b4b52f53d6fdFaulting package full name: Faulting package-relative application ID:any one can have a solution pl postRegards,Dhanya |
| need to get the all jobs information Posted: 05 Aug 2013 10:12 PM PDT HIwe are planning to configure the replication. so we are planning to schedule the snapshot, before scheduling we have to find what ever the jobs are running on the instance and time.how can we find the jobs details with scheduled time is there any query for this? |
| Page file best practices and memory upgrade. Posted: 05 Aug 2013 06:03 PM PDT Hi, we are planning to upgrade the ram in our SQL 2008 R2 cluster running on Windows 2008 R2. Both SQL and Windows are Ent edition. currently the two nodes have 32GB of memory each, we already purchased 2 x 32GB memory upgrades for these servers. Now normally i just hard configure the Windows pagefile to the Windows recommend size but in this case when we upgrade the memory in the server to 64GB the C: probably wont have much free space left to set the Page file to 96GB.If i set the page file to say 72GB the system meory plus 8GB will this be enough for successful crash dumps?Recommendations? |
| You are subscribed to email updates from SQLServerCentral / SQL Server 2008 / SQL Server 2008 Administration To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google Inc., 20 West Kinzie, Chicago IL USA 60610 | |
No comments:
Post a Comment