New answers tagged sql-server-2000
If you want to make sure that Job 2 doesn't start its processing while Job 1 is running, then you could make the first step of Job 2 be a call to sp_help_job, which you can use to check the run status of a job (it's the current_execution_status field).
A further aside that is relevant to your situation: I would recommend passing dates into SQL Server in ISO 8601 format (or a close approximation to it), as that's the least likely to be misinterpreted. SQL Server 2000 seems happy with accepting dates in yyyy-mm-dd hh:mm:ss format.
Can you access the SQL Server from the console? ie, are all the services up & running properly? Assuming that's the case, check the SQL Server Network Utility, make sure all the settings are as you expect. Then, check your SQL Server Client Network Utility settings (both on the server, and the client) - make sure that matches up with expectations. ...
In practical terms from a code or user perspective, no. There is one internally (rid) but it is not exposed in any documented system view or function
High CPU in SQL Server is very often caused by poor indexing Unfortunately, SQL Server 2000 lacks the tools of later versions to track these down easily Saying that, if you run SQL Profiler you will be able to find high CPU queries and start looking at query plans to work out what indexes are missing
As stated by other posters, datetime values are stored as datetime values, not as strings. If you want to get technical, they are stored as two integers - one representing days and the other representing clock ticks (3.33ms for the datetime datatype). I agree with you in not wanting to use CONVERT() on every field. I feel that the correct place for ...
As stated in the comments, dates are not stored as "dates". They are actually stored as numbers. So there is no need to worry about that side of things. You can change the default output though by changing your language setting. EXEC sp_configure 'default language', '23'; GO RECONFIGURE GO This is the setting for British English. You can see all of ...
Yes this is just improved documentation. FAST n has always been the n version of FASTFIRSTROW i.e. a request to the optimiser to choose a plan that will return n rows more quickly if a plan can be identified to do so. It is not equivalent in anyway to requesting the TOP n rows, which is in effect what you would be asking for if the expectation was for ...
The import/export wizard doesn't copy a lot of stuff, the identity property on columns is just one of the things that it doesn't copy. If you don't have a functional backup you'll want to manually script out all the objects from the database first, then copy the data using the import/export wizard. Once your new database is up and running you'll want to ...
Top 50 recent answers are included