2,531 reputation
1523
bio website billfellows.blogspot.com
location Kansas City, MO
age 38
visits member for 1 year, 11 months
seen 1 hour ago
stats profile views 151

Developer, devourer of pie, disciple of databases, dictator of datum, drinker of tea, delirious with alliterative devices

@billinkc


2d
awarded  Nice Answer
May
21
comment Is this a good strategy for importing a large amount of data and decomposing as an ETL?
Presize your data and log files. Make a good faith guesstimate at what size they'll need to be. Also, ensure they aren't set to grow at the default 1 or 5MB and 10% on the log. Besides the VLF issue with the log, it has to zero out the space before it can use it. Depending on your disk, that can be a not-insignificant amount of time. For your mdf/ndf, you can grant Perform Volume Maintenance Tasks to the SQL Server Service account in Local Security Policy/User Rights Assignment and that will allow it to perform instant file initialization.
May
13
awarded  Caucus
May
13
revised Execute a T-SQL job with a different connection string
No thanks needed
May
8
reviewed Approve suggested edit on SQL Server split mdf into multiple files
May
7
comment WorldWide site - should I save UTC or in fixed time?
Nope, look at Samoa they completely moved their timezone forward.
May
6
answered Converting Non Unicode string to Unicode string SSIS
Apr
24
awarded  Custodian
Apr
24
reviewed Approve suggested edit on Slow Response: Initially it's slow and on subsequent restart of the host it works normally
Apr
22
comment SSIS Data Flow Task Slows Down
How do you have your OLE DB Destination configured? What is the commit size? What about transactions, does your package enlist in one?
Apr
10
comment SQL server slow on Xeon machine, fast on Corei7 x990
Also voting to punt this over to dba.stackexchange as you'll get better focus from the DBA crowd
Apr
10
comment SQL server slow on Xeon machine, fast on Corei7 x990
You generate the database from scripts but that doesn't mean it's identical. One very easy thing to overlook is how that data is laid into tables. Data in your fast environment might have been added to the tables resulting in low fragmentation while the hotrod environment paved that data in there in a jacked up manner resulting in heavy fragmentation and/or out of date statistics. This results in SQL Server being told to look for data in one location on disk but having to search until it finds it in another time zone. How do you tell? Post some sample query plans and we can analyze the diffs.
Apr
5
comment Turning on TF610 in SSIS
@AaronBertrand I wouldn't have been able to answer without your post to put me on the trail. I can't spell CBDD (see)
Apr
5
answered Turning on TF610 in SSIS
Apr
5
comment SSIS keeps force changing excel source string to float
How are your C#/VB skills?
Apr
3
awarded  Popular Question
Apr
3
accepted Relating ExecutionInstanceGUID to the SSISDB
Apr
3
answered Relating ExecutionInstanceGUID to the SSISDB
Apr
1
revised SSIS Expressions Date Format get just YY for year
Dirty thiefs taking my answer :)
Apr
1
comment SSIS Expressions Date Format get just YY for year
Are you looking to do this as part of your source query or as an Expression in a component like a Derived Column