network profile
| bio | website | davidwing.pro |
|---|---|---|
| location | Guelph, Canada | |
| age | 44 | |
| visits | member for | 2 years, 1 month |
| seen | Apr 2 at 19:41 | |
| stats | profile views | 18 |
Professional Engineer & SQL Server Technical Specialist
|
Mar 4 |
comment |
Could not allocate space for object 'dbo.History' in database '[path to mdf]' because the 'PRIMARY' filegroup is full @brother -- out of curiosity unrelated to your question, does dbo.History contain two ntext fields? |
|
Nov 22 |
comment |
Connect to SQL Server 2012 Database from 2008 Agent Job containing 2008 SSIS Package Mike, Thank you. I'll mark this as the answer once I try this (and it works). |
|
Nov 8 |
asked | Connect to SQL Server 2012 Database from 2008 Agent Job containing 2008 SSIS Package |
|
Oct 24 |
answered | One database with two schemas: cross-schema View permissions issue? |
|
Oct 23 |
asked | How to display differential backup date in SSMS Object Explorer Details |
|
Oct 19 |
accepted | When was a table trigger disabled and re-enabled? |
|
Oct 19 |
asked | When was a table trigger disabled and re-enabled? |
|
Sep 29 |
accepted | sp_OACreate vbscript.regexp Class not registered |
|
Sep 29 |
answered | sp_OACreate vbscript.regexp Class not registered |
|
Aug 23 |
awarded | Supporter |
|
Aug 23 |
accepted | How do I merge two XML variables in SQL Server (2005/2008)? |
|
Aug 23 |
comment |
How do I merge two XML variables in SQL Server (2005/2008)? Mikael, your solution produces the desired result. Thank you. |
|
Aug 22 |
asked | How do I merge two XML variables in SQL Server (2005/2008)? |
|
Nov 27 |
awarded | Tumbleweed |
|
Nov 20 |
awarded | Editor |
|
Nov 20 |
revised |
sp_OACreate vbscript.regexp Class not registered added 1546 characters in body |
|
Nov 20 |
asked | sp_OACreate vbscript.regexp Class not registered |
|
Aug 23 |
comment |
Alerting on Database Mirroring Events Update from Microsoft "... the underlined issue was identified as a core Engine issue ... will not be classified as a hotfix required for the SQL 2008 or SQL 2008 R2. We will try to address this issue in our current release for SQL 2011 ... the risk for breaking existing functionality by changing the output format (the message format) is fairly high. We decided therefore that we cannot make this change ... workaround is to create your own alert that includes the complete message. See also technet.microsoft.com/en-us/library/cc966392.aspx"; |
|
Aug 5 |
awarded | Fanatic |
|
May 27 |
awarded | Scholar |
