What are you trying to accomplish?...

Rather than adding a single user (who can be deleted or removed over time), create an AD Group or a Local Group, then make the members of that group a member of the [sysadmin] server role. This way, an AD Administrator can add an individual to the gr...

>> Some other packages are running on 64-bit provider too in same machine. I was getting this issue for only for one package among them Are all the packages running under the same security context?...

The problem is you have the 32-bit provider installed, but not the 64-bit provider. By forcing the package into 32-bit mode, it's able to communicate with the provider....

@hicham4 Given that you will have a large number of respondents and large number of questions, it's probably a better idea to perform the pivot in a reporting tool like SQL Server Reporting Services (using a Tablix), Access (using a CrossTab query) o...

The solution provided really isn't appropriate for a pivot. It's more like a column expansion, like this: SELECT [p].[seq], CASE WHEN [p].[ItemColour] = 'Red' THEN 1 ELSE 0 END as [Red], CASE WHEN [p].[ItemColour] = 'Blue' TH...

The problem isn't that the columns have the same name, the problem is that the query processor can't know WHICH column to order by; HumanResources.Employee.BusinessEntityID or HumanResources.EmployeePayHistory.BusinessEntityID The solution is to use ...

That is the nature of the float data type. It is an INEXACT approximate numerical representation and should be rarely used. If you need to store and retrieve a number like 123,456,789, use [int[ with a range of (-2,147,483,648) to (2,147,483,647). ...

Next time, rather than spreading the logs over multiple "drives", create a RAID0 stripe. This way you'll get the benefit of all the drives bandwidth. * RISK * RAID 0 is not fault-tolerant. If you lose one drive, you lose them all....

Why create multiple log files?...