Options for bringing data into a Microsoft SQL Server database
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2015 07:04 AM
Hello,
I am having issues bringing large tables in from the ServiceNow database into a Microsoft SQL Server database. I used the information from the following article: Using ODBC Driver in SQL Server - ServiceNow Wiki. However, I get the following error: OLE DB provider "MSDASQL" for linked server "SERVICENOW_PRAXPROD" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]Disk Cache file size limit has reached[10215]." I went into the ServiceNow ODBC Management Console and reset the ServiceSQLDiskCacheMaxSize property to the maximum, 1,048,575. After doing this, I was still getting the same error.
Are there alternatives to using the linked server approach? If not, is there a way to get around the maximum cache size issue?
Thanks in advance,
SWB
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2015 05:43 AM
Hi Tony and Ashutosh.
I have been able to successfully bring in large tables to the Microsoft SQL Server instance using linked servers. I do this by breaking up the large ServiceNow tables by year, and then doing a UNION ALL on the tables once they are in SQL Server. We may be looking at the Perspectium replicator service as well going forward.
Thanks to both of you for the feedback.
Regards,
Stephen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2015 08:32 AM
Hi Stephen,
Another alternative is SnowMirror . It can replace your solution based on the ODBC driver. SnowMirror simply replicates selected tables from ServiceNow instance into your on-premise SQL Server database.
Kind Regards,
Pavel