while running a perl DBI against MS SQL Server 2008.

Cause: unknown. But the field data size might be relevant (for example, incorrect sampling/guessing of the field size by the ODBC).

Fix: Exclude the field from the query.

This was from SQL Server 2000. This was actually a data truncation problem for me, and apparently for some other people too. If you see this error, check all data sizes whether anything would not fit into the destination field size. How deceiving – the message is.

Solution: Check each field size. Make sure the destination field size is at least the size of the data to insert.

But, it “might be wrong” for advanced uses – the documentation says it is wrong – “if you want to restrict access per branch of the repository.”

But for a simple user like me, it works. All I have to do is add a .htaccess file in the websvn folder, and set config.php correctly.

Altering a column on a Replicated Table

http://www.sqlservercentral.com/articles/Replication/alteringacolumnonareplicatedtable/1666/

However, I was searching for a simpler answer.

Although it doesn’t necessarily say it explicitly, I got a hint from this page.

http://msdn.microsoft.com/en-us/library/ms151870.aspx

The answer is simply, unless there are dependent objects,

1. add a new column

2. update the new column with values of the old column

3. drop the old column

Not sure why this happened…

Fix:

\u mysql

CREATE TABLE `servers` (
`Server_name` char(64) NOT NULL,
`Host` char(64) NOT NULL,
`Db` char(64) NOT NULL,
`Username` char(64) NOT NULL,
`Password` char(64) NOT NULL,
`Port` int(4) DEFAULT NULL,
`Socket` char(64) DEFAULT NULL,
`Wrapper` char(64) NOT NULL,
`Owner` char(64) NOT NULL,

PRIMARY KEY (`Server_name`)

) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT=’MySQL Foreign Servers table’;

source:

http://forums.mysql.com/read.php?11,142598,160503#msg-160503

This was, from…

Wrong setting of ColumnDelimiter= tab when actually it was ColumnDelimiter= comma.

Splendid. Excellent error message.

It’s much easier this way:

1. Create a Data flow task.

2. Use Excel source. Map the names so it matches the destination column name.

- Keep null.

- Adjust maximum length and column type. (Excel driver is lazy.) String is 255 long and columns beginning with number becomes int. For example, (1,2,…,8a, 8b,… ) is assumed as an “int” field.

3. Use oledb destination.

4. Run. It will be in nvarchar and ntext, all over.

5. Run sql scripts – Just do alter table alter column. It’s simpler and easier.

:nvarchar to varchar:    Alter table xxx alter column yyy varchar(500)

:ntext to varchar:           Alter table xxx alter column yyy varchar(1500)

The fix is EnableSendfile Off !

http://httpd.apache.org/docs/2.0/mod/core.html#enablesendfile

EnableSendfile Off

If SELINUX is needed, we need to add context.

The mount script will look like this

mount -t cifs -ouser=USER,password=PASS,ip=xxx.xxx.xxx.xxx,rw,file_mode=0664,dir_mode=0775,uid=xx,gid=xx ,context=system_u:object_r:httpd_sys_content_t:s0 //WINDOWS_SERVER/SHARE /local/mount/point

Not sure but this may also be needed to reset the SELINUX context

fixfiles relabel /local/mount/point

CHECK (column = lower(column))

mysql ERROR 1016 (HY000): Can’t open file: ‘….MYI’ (errno: 145)

It can be repaired.

mysqlcheck -r -p dbname tablename

ref: http://www.databasejournal.com/features/mysql/article.php/10897_3300511_2/Repairing-Database-Corruption-in-MySQL.htm