Viewing 15 posts - 946 through 960 (of 2,612 total)
You cannot do what you are suggesting in T-SQL, even in SQL 2008.
July 22, 2008 at 5:59 am
Why are you using a script task rather than just using an OLEDB Source and destination?
July 22, 2008 at 5:38 am
Using a sub-query like this will not always cause an unnecessary scan, but using a join give the optimizer more choices and it will often generate a better execution plan.
July 21, 2008 at 1:49 pm
What modifications to the default replication have you done? I assume you are using transactional replication.
By default, transactional replication will, as you have said, translate an update to 1000...
July 21, 2008 at 1:44 pm
Ideally, if you can turn on SNAPSHOT ISOLATION it will resolve your blocking issues, but it may cause you some performance issues and bloat your TempDB pretty badly if you...
July 21, 2008 at 1:36 pm
Look in Books Online for the topics on Package Configurations.
July 21, 2008 at 1:32 pm
You have attribute keys that are not unique. Every year has the same 4 quarters. Since you named your Quarters Q1, Q2, Q3, and Q4, the same 4...
July 21, 2008 at 1:28 pm
Posting the execution plans will probably help, and please post the DDL and T-SQL. Seemingly insignificant data differences can cause vastly different execution plans depending on how the queries...
July 21, 2008 at 1:23 pm
I am forced to agree with me as well.
July 21, 2008 at 12:34 pm
SQL Servers will vary depending on the purpose of the database(s) on them. It is a good start to make sure the OS, Data Files, Log Files, and backups...
July 21, 2008 at 9:30 am
It may depend on the type of fork.
A plastic fork would need to be of reasonable quality. A spork would probably not work at all.
July 21, 2008 at 6:48 am
From the CLR, you can do this, but I think you have to run it as unsafe to create a new thread. Also, the context connection is not available...
July 21, 2008 at 6:31 am
Without some sample data and the DDL, this is hard to do, but the triggers need to be on the EMPDET table and I would split the INSERT and UPDATE...
July 21, 2008 at 6:27 am
You may get a better response with some sample data and showing an attempt at doing this yourself.
http://www.sqlservercentral.com/articles/Best+Practices/61537/%5B/url%5D
July 21, 2008 at 6:09 am
No, it is not possible in any version of SQL Server to do that in T-SQL. You would have to run the three queries from three individual connections.
July 21, 2008 at 5:55 am
Viewing 15 posts - 946 through 960 (of 2,612 total)