mssql
3 TopicsError when importing CSV file
Hi, I am new at MS SQL and have the community edition in my local machine. Trying to import a CSV file but getting the following error message: Total Defect Qty:=SUM([Defect Qty]) TITLE: Microsoft SQL Server Management Studio ------------------------------ Error inserting data into table. (Microsoft.SqlServer.Import.Wizard) ------------------------------ ADDITIONAL INFORMATION: Error inserting data into table. (Microsoft.SqlServer.Prose.Import) ------------------------------ The given value '[name of the column]' of type String from the data source cannot be converted to type nvarchar for Column 4 [Label]. (Microsoft.Data.SqlClient) ------------------------------ String or binary data would be truncated in table '[dbo].[name of the file]', column 'Label'. Truncated value: '[name of the column '. (Microsoft.Data.SqlClient) ------------------------------ BUTTONS: OK ------------------------------ Do you think you can help me please? Thanks, NaveenSolved341Views0likes5CommentsHELP with CTE or a Cursor to update multiple rows in 1 table ..selecting from Multiple databases
Server A Syetemtable of Dbname= ABC Dbname productid ABC 123 Syetemtable of Dbname= XYZ Dbname productid ABC 987 Syetemtable of Dbname= AQW Dbname productid AQW 123456 Like we have 1000 DB's in Server A and each db has a system table 1 Main LOGIN info table in Server A Dabatase DB1 SELECT * from DB1. DBO.LOGIN table DBName product ID ABC NULL XYZ A9065 AQW mailto:33c@1442 these rows in 1 main Login table are not matching the system table rows of each individual Databases Now I want to update 1 Main LOGIN info table in Server A Dabatase DB1, so that I get results matching each login table of all db's SELECT * from DB1. DBO.LOGIN table DBName product ID ABC 123 XYZ 987 AQW 123456720Views0likes3CommentsDifferential backups have increased in size.
So in short our differential backups have gone wild. Normally starting from few hundred megabytes and last ones of the day ending somewhere between 10-12 Gigs. That's all normal for us. But we recently have had issues with the next full backup being about 80G or something like when the full backup is normally 50-60G. And when the full backup is about 80G then differentials start at 14G. So needless to say this pretty much eats all the space available on the backup disk. Of course we can add more disk to the machine but that really isn't the best solution since this issue seems to intermittent. Image to clarify what I mean. So then I started looking at the logs. And noticed that there is no log mentioning a successful backup from the 25th, but there is from 24th when the backup is normal regarding size. So my question would be if this is an issue with the full backup? To me it seems that the full backup from 25th isn't sort of registered and and differentials are made against the previous full backup. Logs from full backup 24th day: (successful 56g.) 2022-01-24 01:05:44.09 Backup Database backed up. Database: DB_NAME, creation date(time): 2018/08/14(08:33:06), pages dumped: 775956, first LSN: 9744:300161:237, last LSN: 9744:302244:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\DB_NAME_full_backup_2022_01_24_010002_2306929.bak'}). This is an informational message only. No user action is required. 2022-01-24 01:05:44.11 Backup BACKUP DATABASE successfully processed 775827 pages in 340.326 seconds (17.809 MB/sec). Logs from 25th. No mentions about succesful backup even though it creates a backup with the size of 88g. 2022-01-25 00:09:00.80 spid14s FlushCache: cleaned up 6292 bufs with 1275 writes in 65929 ms (avoided 3489 new dirty bufs) for db 6:0 2022-01-25 00:09:00.80 spid14s average writes per second: 19.34 writes/sec average throughput: 0.74 MB/sec, I/O saturation: 2547, context switches 4073 2022-01-25 00:09:00.80 spid14s last target outstanding: 26, avgWriteLatency 20 2022-01-25 01:07:17.17 spid14s FlushCache: cleaned up 5534 bufs with 1042 writes in 74320 ms (avoided 1200 new dirty bufs) for db 6:0 2022-01-25 01:07:17.17 spid14s average writes per second: 14.02 writes/sec average throughput: 0.58 MB/sec, I/O saturation: 2783, context switches 8284 2022-01-25 01:07:17.17 spid14s last target outstanding: 2, avgWriteLatency 160 We are using MSSQL version 13.0.5888.11 with WS 2k16 build number 14393 Is this a known issue? Are there any known fixes? Thanks in advance1.2KViews0likes0Comments