Viewing 15 posts - 16 through 30 (of 57 total)
Regarding linked servers
Linked servers are the way a SQL Server Instance tracks the
OLEDB provider and connection context that it applies to queries containing four part names. Server.Database.Owner.Object
Rather than using the...
March 23, 2004 at 3:15 pm
Couple of things to check.
First Check that the provider MSDA ->OLEODBC provider is allowed adhoc access. Given your mentioning db2odbc.dll.
Second Make sure the provider support IOpenRowset, IRowsetLocate, and...
March 22, 2004 at 9:10 pm
Well now there you go changing the topic away from philosphy
That sounds more like politics... I.E., they're giving you the corporate norms...
March 22, 2004 at 8:19 pm
Looks like you getting some form of record mutliplication because of flag field that needs to be in the join condition? But it might also be because one of the...
March 22, 2004 at 7:02 pm
Danielle
Check out the work going on in the XMLA space. Perhaps one of these consultants can help you with your needs.
http://www.xmla.org/contact_pub.asp
Personally, I think this local vendor http://www.aspirity.com/ is...
March 22, 2004 at 6:47 pm
Depending on your security requirements for viewing of the METADATA the REPOSITORY features that comes with SQL Server 2k may be all you need. Otherwise you may have to look...
March 22, 2004 at 1:04 pm
Is the flat file an intermediate format or a final format? Why are the column names so important to embedd in the data? Answering these might give you better alternatives.
You...
March 22, 2004 at 12:40 pm
Perhaps this bias toward views stems from dealing with the updateable view paradigms. Thus, almost equivalent to sp. The only difference is would probably be the way parameters are avoided...
March 22, 2004 at 12:30 pm
Carl,
Here's a good article demonstrating all the issues around what I think you've stated to be your problem.
Peter Evans (__PETER Peter_)
March 20, 2004 at 1:17 pm
Carl,
So there's several transcode points involved here. SQL Server Instances code pages constraints which are limited to what ever the underlying os supports and its configured value.
The SQL collations attribute overriding the...
March 20, 2004 at 5:32 am
Carl,
Heres is I believe the two essential points from msdn that apply to your goal as outlined from the previous two posts.
[snip from msdn]
The cultures are generally grouped into three...
March 18, 2004 at 4:43 pm
Carl,
My understanding of this issue is that InvariantCulture is used to keep the data neutral internally until you decide to put it into other .NET Strings or Winform string properties...
March 18, 2004 at 1:04 pm
You don't mention setting the CultureInfo member of the DataSet!
Try setting it to System.Globalization.CultureInfo.InvariantCulture
EG
public DataTable MakeGoodTable()
{
DataTable goodTable = new DataTable("Customers");
// Satisfies FxCop rule:...
March 18, 2004 at 1:53 am
You could use the COLUMNS_UPDATED in an after update trigger
Peter Evans (__PETER Peter_)
This example creates two tables: an employeeData table and an auditEmployeeData table. The employeeData table,...
March 17, 2004 at 11:25 pm
You were on the right track, but it sounds like a command object is warranted
(whatever that may be in ADO.NET). I swear there's been so many sql server
api's...
March 17, 2004 at 10:42 pm
Viewing 15 posts - 16 through 30 (of 57 total)