Viewing 15 posts - 391 through 405 (of 602 total)
I'm not going to include the instructions, but there are a couple things to remember:
SQL installer won't run from a UNC path. You'll either need to copy the contents of the...
March 10, 2006 at 10:19 am
Have a look at Manifold.
It is fairly inexpensive and will probably do what you have described. This is not going to be easy, but the good things never are.
jg
March 8, 2006 at 7:25 am
TFQ: "You are debugging a SQL Server 2000 application and are starting and stopping the SQL Server from the command line. "
This is not ambiguous at all. The question specifically...
March 6, 2006 at 7:25 am
Hello Juanita,
When that counter takes a drastic drop, it is usually caused by a process or processes that are accessing data that is not in memory, and so much data...
March 3, 2006 at 12:09 pm
Check out http://en.wikipedia.org/wiki/B_tree
and http://en.wikipedia.org/wiki/Category:Trees_%28structure%29
There is some fascinating stuff on how trees can be designed and how rebalancing works.
jg
March 3, 2006 at 8:26 am
Jason,
If you are using NetBackup, you can use the bpbackup command. See the online help for details on what parameters to pass.
jg
March 2, 2006 at 10:18 am
I would suggest that if there aren't very many tables that are "one-way", it may be simpler (and easier to maintain) to use merge replication exclusively.
Just don't update the one-way...
March 2, 2006 at 7:23 am
OOPS. I read it wrong. My apologies.
Must drink more coffee before replying.
February 24, 2006 at 6:22 am
February 23, 2006 at 10:17 am
I believe that the join will take longer because the other will simply rasie an error without actually doing any updates.
You can update multiple tables with a single Update. There...
February 23, 2006 at 10:09 am
A blind squirrel trips over a nut every now and then.
heh
February 23, 2006 at 8:22 am
I got about 1.5 GB when I did the raw math.
Row size = 236 bytes. 20*9 (numeric 13) = 180 + 16 (guid) + 40 (10 ints) = 236 bytes.
6581010 rows * 236 bytes...
February 23, 2006 at 6:52 am
If you have 2 rows in a table that are duplicates, and you wish to delete only one of them, it would appear to be impossible, since any delete statement...
February 22, 2006 at 2:35 pm
Another possible thing would be if the "query" uses a cursor or other looping construct to build a recordset in a staging table, you could get much longer execution times...
February 22, 2006 at 2:19 pm
As Krishnan shows, the standard output from the command shell can be captured in a table. The solution is lacking, however, in that it will only return one row from...
February 22, 2006 at 7:22 am
Viewing 15 posts - 391 through 405 (of 602 total)