130 reputation
19
bio website
location
age 35
visits member for 1 year, 11 months
seen Oct 22 at 5:12

I believe that technology can get us out of this mess we're in. It's the last, best hope.


Oct
17
awarded  Notable Question
Sep
24
awarded  Autobiographer
Jul
3
awarded  Curious
Mar
28
awarded  Promoter
Mar
26
comment Why would you use a managed service account rather than a virtual account in SQL Server 2012?
It can't be all that atypical. VAs, which "use the permission of the machine account", are the default account type for almost all the MSSQL12 service accounts. Either MS left out a sentence like "however, it is not recommended to use VAs to access the network in a domain" or this is precisely what is intended. That is why I asked the question.
Mar
25
awarded  Commentator
Mar
25
comment Why would you use a managed service account rather than a virtual account in SQL Server 2012?
So if "all virtual accounts use the permission of the machine account" then by this definition, it couldn't possibly "access the network in a domain environment".
Mar
25
revised Why would you use a managed service account rather than a virtual account in SQL Server 2012?
added 853 characters in body
Mar
24
revised Why would you use a managed service account rather than a virtual account in SQL Server 2012?
edited tags
Mar
24
asked Why would you use a managed service account rather than a virtual account in SQL Server 2012?
Mar
5
comment How can I get more information about which lookup failed in an SSIS lookup?
re: debugging in VS, the Data Viewer allows me to see what's going into the Lookup, but I still can't see what failed. I can add a Data Viewer to the No Match output but a breakpoint in the script is the way to go for investigating strange text-matching issues.
Mar
5
comment How can I get more information about which lookup failed in an SSIS lookup?
NB: the output of ComponentMetaData.FireWarning appears in debugging output.
Mar
5
accepted How can I get more information about which lookup failed in an SSIS lookup?
Mar
5
awarded  Supporter
Mar
5
asked How can I get more information about which lookup failed in an SSIS lookup?
Feb
3
comment In the Import/Export Wizard inside SSDT, why is the MSAccess DB Engine data source looking for a workgroup information file?
@JonSeigel It's already uninstalled. Executing the package with the utility works as expected. I can live with 32-bit MSA drivers for what I'm doing, though I'm still unclear about what was happening here.
Feb
3
comment In the Import/Export Wizard inside SSDT, why is the MSAccess DB Engine data source looking for a workgroup information file?
Also, I have noticed that by uninstalling the 64-bit 2010 redist and installing the 32bit version, this problem is solved. But then I can no longer use the 64-bit Import/Export Wizard because it refuses to install both 32- and 64-bit 2010 redists.
Feb
3
comment In the Import/Export Wizard inside SSDT, why is the MSAccess DB Engine data source looking for a workgroup information file?
VS10 Shell seems to be a 32-bit app. However, I see a flag in Project properties -> COnfiguration Properties -> Debugging -> Run64BitRuntime == True.
Feb
3
asked In the Import/Export Wizard inside SSDT, why is the MSAccess DB Engine data source looking for a workgroup information file?
Oct
10
awarded  Popular Question