meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 1 month |
| seen | 54 mins ago | |
| stats | profile views | 18 |
|
Jun 12 |
comment |
Database associative table I think this is entirely subjective to the business process being modeled. I don't see any point in adding a record to a relationship table to represent the absence of a relationship. |
|
May 29 |
comment |
Efficient way to fetch records since a given criteria As long as you have an appropriate index on ID, I don't think the top (n) ... where ID > @id construct is going to be your problem. It sounds like you need to tune the complex joins. |
|
May 16 |
comment |
Fixed length text file insert into SQL table Not having experience with FORMAT FILE, I've looked into it briefly, but I haven't seen an example that addresses files like the example, where the header has one set of columns, the data rows another, and the footers another. Can you suggest a source for info? |
|
May 16 |
comment |
Fixed length text file insert into SQL table In my very limited experience, SQL isn't as bad at string manipulation as everyone says--this is how I'd try it if SSIS vaporized itself, and if the performance wasn't acceptable, I'd try something else. |
|
May 6 |
comment |
pros/cons of different ways to store whether a record is one of two options? I can't vouch for best practice, but I'd go with option 3. You can make it a bit if you're sure you only need the two options, and changing it to an int later (if your prognosticator is faulty) would probably be significantly easier than fixing one of the other options. Probably not a bad idea to still build the corresponding AddressType table for a reference, even if you don't code to use it. |
|
Oct 3 |
comment |
Heap size too large for data present I rebuilt the table and it's now less than 14 MB. Y'all were leading me to it, but I think looking up DELETE WITH (TABLOCK) made it sink in why the pages weren't being deallocated. The simplest explanation seems to be that the table was once loaded with way too much data, and those pages have been allocated ever since. I notice now that avg_page_space_used_in_percent has jumped greatly, so that may help me find other offenders. |
|
Oct 3 |
comment |
Heap size too large for data present The package for this table uses a DELETE when most of them use TRUNCATE, but it's not the only one. Other than that, it's just an ODBC destination in a very simple data flow. |
|
Oct 3 |
comment |
Heap size too large for data present Interesting info, but in this case, this query returns the expected layout |
|
Oct 2 |
comment |
Heap size too large for data present For the same reason the columns are all 50 or 255 wide--because it defaulted that way and no one knew better. I'm out to fix it, but I want to make sure I understand it as much as possible. We have hundreds of similar tables; this is the only one I've noticed this bloat on, but I'd be surprised if it's the only one. |
