RhinoETL无法连接到sql服务器

发布于 2024-12-29 22:11:33 字数 635 浏览 1 评论 0原文

我确信，我在这里遗漏了一些明显的东西。我正在尝试让我的基于 RhinoETL 的示例应用程序与 sql 服务器通信。它只是不会那样做。我正在关注 Paul Barriere 的视频教程。

using Rhino.Etl.Core.Operations;
namespace RhinoETLTest01.Operations
{
class WriteJoinedRecordsToSql : SqlBulkInsertOperation
{
    public WriteJoinedRecordsToSql() : base("TestEtl", "dbo.NameAndTitle") {}

    protected override void PrepareSchema()
    {
        Schema["Id"] = typeof(int);
        Schema["FullName"] = typeof (string);
        Schema["JobTitle"] = typeof (string);
    }

}

。

我能够合并两个文件中的数据并将它们写入第三个文本文件中但是，我无法将合并的记录放入 SQL 表中。请问我缺少什么？我的 App.Config 具有正确的连接字符串设置。

谢谢

原文

I am sure, I am missing something obvious here. I am trying to get my sample RhinoETL based app to talk to a sql server. It just would not do that. I am following the video tutorial by Paul Barriere.

using Rhino.Etl.Core.Operations;
namespace RhinoETLTest01.Operations
{
class WriteJoinedRecordsToSql : SqlBulkInsertOperation
{
    public WriteJoinedRecordsToSql() : base("TestEtl", "dbo.NameAndTitle") {}

    protected override void PrepareSchema()
    {
        Schema["Id"] = typeof(int);
        Schema["FullName"] = typeof (string);
        Schema["JobTitle"] = typeof (string);
    }

}

}

I am able to merge data from 2 files and write them into a 3rd text file. But, I cant get the merged records to get into a sql table. What am I missing please? My App.Config has the correct connectionstring setting.

Thanks

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

も星光 2025-01-05 22:11:33

我有类似的问题。解决方案是在 App.config 中的连接字符串中完全限定 sql 提供程序

<configuration>
  <connectionStrings>
    <add name="TestEtl"
       connectionString="Data Source=TestEtl;Initial Catalog=NameAndTitle;Integrated Security=SSPI;Timeout=300;"
       providerName="System.Data.SqlClient.SqlConnection, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
  </connectionStrings>
</configuration>

，然后检查 sql 命令的正确性。我下载了完整的源代码并逐一查找这些问题和相关问题。

I had a similar problem. The solution was to fully qualify the sql provider in the connection string in the App.config

<configuration>
  <connectionStrings>
    <add name="TestEtl"
       connectionString="Data Source=TestEtl;Initial Catalog=NameAndTitle;Integrated Security=SSPI;Timeout=300;"
       providerName="System.Data.SqlClient.SqlConnection, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
  </connectionStrings>
</configuration>

After that check your sql commands for correctness. I downloaded the full source and stepped through to find these and related issues.

回复收藏 0 原文

~没有更多了~