network profile
| bio | website | movingsql.com |
|---|---|---|
| location | New Jersey | |
| age | 55 | |
| visits | member for | 1 year, 1 month |
| seen | May 13 at 16:43 | |
| stats | profile views | 56 |
coder & programmer of many defunct languages...
|
Aug 5 |
comment |
Sql Server Linked Server That is not an error from SQL Server error. There must something else going on here that you're not telling us. |
|
Aug 4 |
answered | Documenting a giant web of inter-related stored procedures in an MS SQL database: What tool or format? |
|
Aug 2 |
comment |
Can SQL Express be used as a Log Shipping monitor server? Yes the setup does check the edition but that's just a safety check. You can override that by hand if you want (probably not supported), but it still can't work because there's no Agent to run the Monitor job(s). Maybe that's jsut semantics on my part ... :) |
|
Aug 2 |
comment |
Can SQL Express be used as a Log Shipping monitor server? SQL Express doesn't have SQL Agent does it? I'm pretty sure that's the reason it can't be done... |
|
Jul 26 |
comment |
Bulk grant execute permissions for scalar functions & stored procedures +1: Heh, very nice. |
|
Jul 24 |
comment |
Attempting to tune a Sharepoint site using SQL Server Waits and Queues Trying to tune Sharepoint's SQL Server usage is an excercise in extreme futility and dangerous levels of frustration. You cannot add, modify or remove any of the indexes and stay supported. The only good news there is that it probably wouldn't matter if you could, because the real problem with Sharepoint is it's SQL code (especially the list processing code) which is a text book in how not to do such things in SQL Server. In fact, it will really make you question how Sharepoint and SQL Server could have been written by the same company. |
|
Jul 22 |
comment |
How does the database decide which Index to use SQL Server determines the index to use largely from statistics, and you do not have enough data in these tables for it to matter. SQL Server knows this ... |
|
Jul 19 |
comment |
Stored Procedure to return dynamically created table data Give us a range then. It matters a great deal. |
|
Jul 18 |
comment |
Stored Procedure to return dynamically created table data I'm afraid to ask, but, "How many tables?" |
|
Jul 15 |
comment |
Optimising MySQL Is there an index on {post_name, post_type, post_date}? If not, add it and see if that fixes it. |
|
Jul 14 |
awarded | Revival |
|
Jul 14 |
revised |
Tempdb is getting full very quickly in microsoft sql server 2008 added 1 characters in body |
|
Jul 14 |
awarded | Critic |
|
Jul 14 |
answered | Tempdb is getting full very quickly in microsoft sql server 2008 |
|
Jul 14 |
comment |
Stored procedure compilation blocking due to many parameters to sp_executesql @Tadmas: Could you provide a shortened example of how these parameters are being used here in both levels? |
|
Jul 14 |
comment |
Stored procedure compilation blocking due to many parameters to sp_executesql And FWIW, I actually agree that the whole approach to this procedure probably needs to be re-examined, but without a clearer example of what's actually going on and what's being done with these parameters (at both levels) there's not much more that we can suggest. |
|
Jul 14 |
comment |
Stored procedure compilation blocking due to many parameters to sp_executesql @Tadmas: If the dataTypes are that different, then you could use sql_variant's in the #temp table definition instead. They're not usually recommended, but should be OK for this situation. |
|
Jul 14 |
comment |
Stored procedure compilation blocking due to many parameters to sp_executesql @Aaron Bertrand: As Tadmas indicates here, it was my understanding that the problem was coming from binding the parameters in the sp_executesql call, which is why I took this approach and rather than one more like your answer. |
|
Jul 14 |
revised |
Stored procedure compilation blocking due to many parameters to sp_executesql added 16090 characters in body |
|
Jul 14 |
answered | Stored procedure compilation blocking due to many parameters to sp_executesql |
