Viewing 15 posts - 16 through 30 (of 45 total)
As long as the prodcution nodes are configured to use a static amount of memory you should be ok. But, the 3rd node needs to be sized to...
October 30, 2007 at 11:52 am
--here's documentation I've prepared for my group--
(btw: no need to change the database mode from Full to Simple)
Large transactions cause the transaction log to grow.
When you do a clean...
October 30, 2007 at 11:42 am
For a 200Gig database, I suggest using SQL LiteSpeed. If the database is 200Gig native, the backup file may be as small as 30 Gig with SQL Lite Speed....
October 30, 2007 at 11:27 am
/*
I use smtp mail. I find this method far simpler that DTS.
Export the data to a text file using osql. Attach the text file to the email and...
October 30, 2007 at 10:48 am
Most SQL servers that host Blackberry database have issues that require a reboot. They create large tempdb databases and they don't clear up connections properly. Eventually, the server...
October 30, 2007 at 10:27 am
In many cases I've been able to resolve this by logging into the SQL Server, opening enterprise manager and ensuring the server is registered using the computer name, NOT (local)....
October 30, 2007 at 10:21 am
I've never found a way out of this. However, before you fix the problem, you should investigate the cause. Look at all the logs for a clue...
October 30, 2007 at 10:02 am
you could script the entire database schema (no data) and recreate a new training database.
Create a dts package to migrate some data. If you have referential integrity, this could...
October 10, 2007 at 1:40 pm
How about: script the existing user table and recreate using a different table name. what happens when you use the new table?
are there any "check constraints"? ...
October 3, 2007 at 11:40 am
there must be something we don't know about here. I set my compat level to 8, recreated the tables and ran the code with no issue.
I strongly suggest a...
October 3, 2007 at 11:02 am
the use of the =* operator and the boolean datatype are throwing me here. Neither are supported in SQL Server.
=* is non-ansi.
Do you have database compatibility level set? ...
October 3, 2007 at 10:44 am
What platform is the database Remus located?
October 3, 2007 at 10:38 am
I see no reference in the insert statement to the field that is causing the error.
For this reason, I suspect there may be a trigger on the insert? ...
October 3, 2007 at 9:09 am
what service account are your sqlserver services running under? Are they running under a domain account with the correct priv?
October 3, 2007 at 8:14 am
Viewing 15 posts - 16 through 30 (of 45 total)