SQLite to MS SQL – Import Script Using Linked Server

-

This post continues the previous article about connecting SQLite to SQL Server using an ODBC driver and a Linked Server.

The script below retrieves table metadata from the SQLite linked server into a table variable and prepares a cursor over the table names. This can be used as a base for further automation or dynamic import logic.

Retrieve Table Metadata


declare @temp table
(
    col1 varchar(255),
    col2 varchar(255),
    [name] varchar(255),
    [type] varchar(255),
    col3 varchar(255)
)

insert @temp exec sp_tables_ex 'Your_LinkedServer_Name'
select * from @temp

Create a Cursor Over Table Names


DECLARE lstTables CURSOR FOR
select [name] from @temp

Important Notes

  • The Linked Server must already be configured using the MSDASQL provider.
  • The ODBC DSN must be created as a System DSN, not a User DSN.
  • Make sure the DSN name matches the one used when creating the Linked Server.
  • Do not use spaces in the DSN name to avoid query issues in SQL Server.

Summary

This script extracts table information from a SQLite linked server and prepares it for iterative processing. It serves as a foundation for building automated migration or synchronization routines between SQLite and SQL Server.

Comments

Post a Comment

Popular posts from this blog

Decimal number issue from server to client. Wow! Didn't expect this @_@

-
Image
Chapter 17   where a poor Decimal Number came from Server Side to JavaScript I worked on a page for days, adjusting the UI with CSS and HTML. Everything looked fine… until I started testing multi-lingual support. English — OK. Spanish — OK. Chinese — OK. Even right-to-left Hebrew (crooked and askew, but working). But Russian? Nope. In Russian the page stopped working completely: only static texts and images were visible. Nothing dynamic rendered. Of course it was a JavaScript error. Firefox DevTools showed this: That error led me to this JS code: I stared at those lines and saw nothing wrong — no missing variables, no typos, nothing obvious. I went to the original project code to find the exact non-rendered rows and noticed a server variable embedded into the client-side script: Which naturally led me to the server-side C# code responsible for generating that value: Nothing looked wrong there either. So I did what every developer does in ...
Read more

Shrinking node_modules for AWS Lambda (My First “npm shock” and a Practical Fix)

-
Image
I’m a newbie in Node.js and not really familiar with the whole npm ecosystem. I honestly didn’t expect that a single npm install would explode into ~10MB spread across ~30 different folders. After a few minutes of staring at it, I realized what’s actually inside those folders: not just runtime code. What shocked me Inside node_modules you get everything: README files source files tests examples docs And then the next level of madness: modules inside modules . Duplicated dependencies nested multiple levels deep (e.g. inherits , core-util-is , tedious …), even if they already exist elsewhere in the project tree. Here’s a typical example: I’m in node_modules → package bl , and there’s another node_modules folder inside it, plus test , README and other “junk”… all for a ~10KB JS file. The obvious assumption (that turned out wrong) Once I accepted the chaos, I assumed there must be a “build for production” command that would “compile” depende...
Read more