|
Topic: |
Updating a table with many rows |
|
Added: |
11/27/2007 7:30:29 PM |
|
|
If you see the message:
'xxxx' table
- Unable to modify table.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
You can adjust the timeout parameter to fix:
http://support.microsoft.com/?kbid=915849
Quote from Microsoft:
The table and database designers in SQL Server Management studio have a default transaction timeout of 30 seconds. If the transformation that has been requested requires the table to be recreated (for example, if you want to change the order of the rows in the table) and the data in the table is large, it can take much longer than 30 seconds to copy the data to the new table.
You can increase the transaction timeout in SSMS in the Tools | Options | Designers | Table and Database Designers dialog. Obviously, if you set the timeout to a very large number and there is a network or other problem, you won't find out about it until the timeout expires, which could be several hours if you make the timeout large enough.
Users should also be aware that if a table edit requires a table recreate, the table will be locked until the transaction completes, which will prevent queries and stored procedures from operating on the table while it is being edited. Great care should be taken using the table and database designers against production databases where making the data unavailable for extended periods of time (up to the designers transaction timeout) is not acceptible.
|
|
|
Topic: |
Display the recovery model for all databases |
|
Added: |
8/15/2007 10:32:00 AM |
|
|
Use the following query to display the recovery model for all databases:
SELECT name, DATABASEPROPERTYEX(name, 'Recovery')
FROM master.dbo.sysdatabases
ORDER BY 1
The "Recovery type" should be "Full" for the transaction log backup to work properly. Otherwise, you will get an very uninformative message that the job failed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Topic: |
Crystal Reports: Error: "Load Report Failed" in a Visual Studio .NET web application |
|
Added: |
10/9/2006 10:19:00 AM |
|
|
Crystal Reports: Error: "Load Report Failed" in a Visual Studio .NET web application
Read article here.
|
|
|
Topic: |
Dealing with MS SQL Tables that contain Duplicate Rows |
|
Added: |
9/29/2006 2:44:23 PM |
|
|
Dealing with MS SQL Tables that contain Duplicate Rows
http://www.databasejournal.com/features/mssql/article.php/2235081
select stor_id, ord_num , count(*) as 'Num of Dups'
from pubs.dbo.sales
group by stor_id, ord_num
having count(*) > 1
|
|
|
|
|
|
|
Topic: |
Procedure to set up a remote access user on Quickbooks |
|
Added: |
8/26/2006 2:35:51 PM |
|
|
Procedure to set up a remote access user on Quickbooks:
1. Login to the administrator account
2. Run desktop icon "Active Directory Users And Computers"
3. RIGHT-click the user->properties
4. On the "Member Of" tab, Add "Domain Power Users" and "Remote Desktop Users"
5. On the "Sessions" tab, set "End a disconnected session:" to "1 minute"
6. Log in to the users account and run the following procedure:
Try running QuickBooks in Windows compatibility mode (Windows XP only).
a. Right-click the QuickBooks shortcut on the desktop and select Properties.
b. Click the Compatibility tab in the Properties window.
c. Put a checkmark in the box labled Run this program in compatibility mode for:
d. From the pull-down menu underneath the checkbox, select Windows 2000.
e. Click OK and start QuickBooks.
Quickbooks reference:
http://www.quickbooks.com/support/faqs/qb2006/b21c8880.html?source=rd_error1
|
|
|
|
|
Topic: |
MS Access memo fields in SQL Server 2000 |
|
Added: |
8/13/2006 1:55:26 PM |
|
|
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=14504
In SQL Server 2000, you have a couple of choices. Varchar (or nvarchar for Unicode data), which has a maximum size of 8000 bytes (4000 for nvarchar). If that isn't large enough, then take a look at the text data type, which allows you to store data up to 2 GB per column. The downside to the text data type, is that you need to use specific statements such as READTEXT and WRITETEXT rather than the standard statements like INSERT or SELECT. Take a look at the topic 'Managing ntext, text, and image Data' in SQL Server 2000 Books Online.
In SQL Server 2005, you should consider the varchar (max) data type. Like the text data type, it holds up to 2 GB, but uses the standard T-SQL statements such as SELECT, INSERT, UPDATE etc. See the topic 'Using Large-Value Data Types' in SQL Server 2005 Books Online.
|
|
|
|