| Thread | Last Post | Replies |
|
| SQL Server Failed Assertions | 04 Jul 2008 00:04 GMT | 5 |
I'm running SqlServer-2005 SP2 x64 I am getting the following 2 Failed Assertions: SQL Server Assertion: File: "xact.cpp" line = 2879 Failed Assertion = '!m_updNestedXactCnt' Trying to use the transaction while there are 1
|
| Trouble with SQL2005 sp_cycle_errorlog | 03 Jul 2008 22:16 GMT | 1 |
We reboot our servers only once a month for patching and so we cycle the SQL errorlogs twice a week to keep them to a reasonable size. Every now and again a problem happens with our SQL Agent job that cycles the errorlog. Last night the job reported as run successfull but a new ...
|
| Backup schedule settings won't save | 03 Jul 2008 21:02 GMT | 2 |
I have a maintenance plan set up and the optimization and indexing schedules are ok. The problem is the schedule for the backup does not save. When I am in the Complete Backup tab to schedule the backup, the dropdown list to remove files older than time increment (days, weeks...) ...
|
| Issue with unclaimed space | 03 Jul 2008 20:49 GMT | 20 |
I am not sure whether someone has experienced the same issue as I do. I have a table which has a column with text data type and a few other regular columns (int, datetime etc). There are inserts / deletes on this table, but the weird thing is the table is keeping on growing, but ...
|
| SQL 2000 accessing DB2 | 03 Jul 2008 20:16 GMT | 6 |
I have a stored procedure that calls remote query using a linked server. It works fine when I run it manually through the Query analyzer window, but when ever I try to schedule it as a job it fails with: Could not create an instance of OLE DB provider 'IBMDASQL'. [SQLSTATE
|
| Selecting Top N within a group | 03 Jul 2008 17:38 GMT | 6 |
I have a table that looks like this: ACCOUNTID DATE aaa 01/01/08 aaa 02/01/08
|
| Proxy Credentials Frustration | 03 Jul 2008 17:09 GMT | 7 |
Please let me know I'm not crazy. I have a NAS that I want to back up to. It has a user account, we'll call him Bob. Lets say I have a folder \\NAS\Backuphere\ which, if I'm logged into my computer as "bob" with the same password that bob
|
| odbc access - not visible tables | 03 Jul 2008 17:00 GMT | 3 |
I'm running Sql2005 sp2 and created a couple of tables within there own schema(for security reasons). I then created a group within AD a gave that group read/write/update permissions those tables within that schema. I then have my users try and connect to the tables via Access an ...
|
| FOR XML data vs Recordset | 03 Jul 2008 16:24 GMT | 1 |
I have an option to return data from a stored procedure using XML or recordset. I do not intend to do any sort of XSL or anything but would be transforming them into typed objects in the Data access layer. Does anyone know of the performance differences when a stored
|
| need to justify upgrade from SQL 2000 to SQL 2005 | 03 Jul 2008 15:32 GMT | 3 |
How can I get our dev/business communicty to upgrade from SQL 2000 to SQL 2005. We are years behind. Is there any link to where I can show them that MS is no longer supporting SQL 2000 or is it ? Thanks
|
| SQL 2005 32 bit code vs 64 bit code | 03 Jul 2008 14:38 GMT | 2 |
We have developed and application in 32 bit SQL 2005 some of our clients are using 64 bit SQL 2005. My question is: if I transfer my 32 bi DB into 64 but enviroment would it work or I might have issues? TIA
|
| SQLServer2005\DatabaseDiagram\Owner | 03 Jul 2008 14:36 GMT | 3 |
I have a database that my client sent me for testing an application on. I setup a new database with the same name as my clients server was using and did a restore to get it installed on my machine. I was wanting to do a Database Diagram of it, but when I try to open up the
|
| MSSQL code to find all records within 1 year | 03 Jul 2008 14:03 GMT | 6 |
Does anybody have a good code for defining records to those within 1 year. We have a field (closingdate) and so we need to show all records for up to 1 year after their closingdate. Thanks
|
| keep identity on inserts | 03 Jul 2008 13:22 GMT | 14 |
I exported some data into a clean table and I got an errror, something about it couldn't reset the primary key values because KEEPIDENTITY was turned off. So I did the export over and I tried to turn KEEPIDENTITY on so that I could use the key values from the export
|
| Query running slow in production | 03 Jul 2008 13:01 GMT | 10 |
First here is my setup. I have a two node active/passive SQL 2005 Enterprise 64bit cluster. There is a database (DB1) that is set up for snapshot replication to another SQL 2005 64 bit server. The replication runs once a night around 2:00am.
|