Viewing 15 posts - 1,216 through 1,230 (of 7,168 total)
Sergiy (4/26/2013)
opc.three (4/26/2013)
April 26, 2013 at 10:20 am
As a side note, using sp_executesql is pretty much how every query from SMO (objects used by SSMS) is issued against the instance. The SQL Agent team coded their queries...
April 26, 2013 at 9:19 am
RSS Feed http://blogs.msdn.com/b/sqlreleaseservices/rss.aspx (courtesy of Gail Shaw for initially providing on these Forums)
April 26, 2013 at 9:14 am
Jeff Moden (4/26/2013)
April 26, 2013 at 9:07 am
Jeff Moden (4/26/2013)
opc.three (4/25/2013)
April 26, 2013 at 7:06 am
I never said a regular PowerShell session offers more security than a regular cmd shell session when not running via xp_cmdshell. I said PowerShell is more robust than cmd shell...
April 25, 2013 at 11:38 pm
All things being equal, going from VARCHAR to NVARCHAR should roughly double the size of your table. You might check for fragmentation in your clustered index (assuming the table is...
April 25, 2013 at 10:03 pm
If you add a CHECK CONSTRAINT to LINE_CODE on all your tables to let the optimizer know what values can exist in that table then the optimizer will be able...
April 25, 2013 at 9:58 pm
Can you please post the DDL for one of the TB tables, including all constraints?
April 25, 2013 at 7:37 pm
That's one way to try and abstract the poor table-design. When used in a query, the Optimizer will evaluate the contents of the VIEW so indexing on the referenced tables...
April 25, 2013 at 3:59 pm
Jeff Moden (4/24/2013)
opc.three (4/24/2013)
April 24, 2013 at 10:05 pm
How are you checking the table size?
April 24, 2013 at 2:50 pm
Jeff Moden (4/24/2013)
opc.three (4/24/2013)
April 24, 2013 at 1:14 pm
Revenant (4/23/2013)
opc.three (4/23/2013)
ImpasseIt's called "deadlock," among us SQLS pros. 😉
Heh...a SQL Pro would also know "it depends" on the context and environment 😉
April 24, 2013 at 8:05 am
Viewing 15 posts - 1,216 through 1,230 (of 7,168 total)