Tag Info

New answers tagged

0

One quick approach to figure out the structure and delimiters of your files would be to use a desktop application with a data import function. MS Excel works very well for smaller files but I find MS Access works very well for larger files and has the advantage of suggesting suitable data types that can port over to SQL Server later. You can toggle the ...


0

Can you contact the supplier of the files to confirm the delimiter? Using the SQL Server import process can help identify but knowing for sure what the delimiters are up front is a better idea. When you say sort the files what do you mean and what is the ultimate outcome of the data? if you just need to merge the files there are other options than SQL ...


1

When using a databse to sort the data one needs to know the structure of the data. In other words, there must be a field delimiter and a row delimiter. Then you can import the file into a SQL-table and index it and sort it the way you want. Importing flat files is easy done with tools provided by any Database Engine, for example SQL Server Integration ...


0

There is no performance difference between single base and number of bases, because "schema" is just the domain of authority. Grouped together or aparted, tables stored and processed in the same way. From the administrative point of view multiple bases are bit preferrable as far as you can dump the whole data for single client by DB name, not the pattern for ...


0

We are doing something very similar at my place and this very question was in my head for a while a few weeks back. After noticing that logs were consuming 98% of our DBs in SQL Server I did some research on how we should handle this problem. It all depends on the structure of your logs but our logs are not really relational so storing them in a RDBMS and ...


0

If you foresee that moving to Cassandra is definitely in your future, it will be easier to do while your dataset is still small and manageable. Also, as you learn and get a feel for Cassandra, a small dataset is a better one to make mistakes on (and thus, easier to correct them). That way your data model is solid by the time your dataset gets big, and ...


0

Option One, Make a new table referencing the id of the Parent/Child Relationship Pros If you need to obfuscate the data, or generate a GUID, or a custom id for an external department working with the data, this might be a valid option to consider. Cons It's not useful for any other situation that this first person can think of. Option Two, Use the ...



Top 50 recent answers are included