sql server 2008

SSIS: Workaround to two errors for no apparent reason when we insert data in MySql

  • Star
  • Star
  • Star
  • Star
  • Star

SSIS: Workaround to two errors for no apparent reason when we insert data in MySqlFor whatever reason we may have to develop a Microsoft Integration Services package we move data from any source to a table that is in a MySQL database.

The first aim will do so through an ADO.NET Destination and MySQL provider for the connection. If we do well to insert the data directly, to create the target, select the connection and then select the table appears an error like the following check everything with the preview or try and do the assignments...

 

 

 

SQL08: affinity_mask, IO_affinity_mask and like riding two on a single server environments without being "walked"

  • Star
  • Star
  • Star
  • Star
  • Star

We put ourselves in position
In our environment we may need to have two replicas of a / s data base distinct environments (the classic example would be production and test). In deciding as we do the most common questions we must ask ourselves are:

- Is this new environment will be temporary? Does large data bases in terms of volume and / or load to be borne is high (even test)?
- Is there version SqlServer2008 development? That alone is at hand if you have an MSDN subscription ...
- Is there an extra server?

Based on these questions and all that it can happen one can opt for different solutions:
"The easiest and if the database to bear the burden are small we can use the same server for all databases (created on the same server with different names (_test) and Holy Easter ...). In order not to disturb each other we can use Resource Governor.
"The most" aseptic "if resources permit and where it would be worthwhile to mount on different servers (if we have the development version)
"Another option is a mixture of the above. Fit the two environments on the same server but different instances.
-Etc ...

1 server cpu n (n> 1) + 2 = 2 instances environments

SQL08: Synchronization Database Microsoft Dynamics AX 2009 on SQL Server 2008

  • Star
  • Star
  • Star
  • Star
  • Star

For those database administrators who have to deal with such a Dynamics Ax 2009 and his henchmen (developers, consultants, etc. )  I leave here a couple of things you should know (or I should say) when we join ax2009 and sql server 2008. Sometimes you can point to the database as a source of the problem but not always. Some requirements to consider for installing Ax2009 are that the user you want access to the system should be user and DOMAIN in sql server role must be a member of securityadmin dbcreator and to create the new database from Ax installer. Once installed (or during the installation process) the problem with the database that we can find include: