Database

Thanks a lot.

That was a good answer!! covered lots of things. thanks for sharing Believe Yourself™

Wow this is very useful! Thanks a lot! :thumbsup: Rafferty

Thank you that did the trick! ;) thx for all the help

Thanks!   I found it using Google and grabbed a copy. :-D "A Journey of a Thousand Rest Stops Begins with a Single Movement"

Can anyone please help me? I still can't figure out how to write this....

Luc Pattyn wrote: the 'Œ' character (and eszet 'ß' and most accented characters used in Western languages) is part of code page 1252, whereas the French Franc and most other (possibly obsolete) monetary symbols are not. Not even the need for a CHCP 1252, since it gets stuffed into a unicode field. Question seems answered though, I'll wait for the repost :-D I are Troll :suss:

I'm facing the following error: Output SqlScript: EXEC master.dbo.xp_cmdshell 'mkDir "C:\ComName\Test\Test Folder 1"' -- It works fine But when I try like EXEC @SqlScript ,it raise the following error. Msg 203, Level 16, State 2, Procedure spCreateF0lder, Line 19 The name 'EXEC master.dbo.xp_cmdshell 'mkDir "C:\ComName\Test\Test Folder 1"'' is not a valid identifier. Thanks Md. Marufuzzaman Don't forget to click [Vote] / [Good Answer] on the post(s) that helped you. I will not say I have failed 1000 times; I will say that I have discovered 1000 ways that can cause failure – Thomas Edison.

I use ArcInfo at work, and I know the nightmare you're talking about.   We intially paid a consulting company to map our electrical utility system and provide us with a geodatabase and supporting shapefiles. Since then the tribe has created a GIS office to provide mapping services, and they've been very helpful by providing files to add to our system.   But finding those files and organizing them in some logical fashion that makes it easy to locate specific feature sets is a hellish task. Re-organizing them is out of the question; if I move a file it will break every map ever created that depends on it. There is no tool I know of that will automatically revise .mxd files with new locations for the files that move. The file names that the GIS group uses don't in any way indicate what the files may contain, so a simple search isn't very helpful. I like the idea of creating an index that can be searched; the keys have to be meaningful, though, and should be accompanied by a detailed description. The keys should not be arranged by project.   They have to include keywords that a user would select to describe a particular feature set - "power poles in Section 10" for instance. "A Journey of a Thousand Rest Stops Begins with a Single Movement"

Asuuming your backup is something like this, and you have the Database Recovery Method set to FULL:: BACKUP DATABASE TestDB TO DISK = 'e:\backups\TestDB.bak', WITH FORMAT, MEDIANAME = 'TestDB_MediaSet1' BACKUP LOG TestDB TO DISK = 'e:\backups\TestDB_log.bak' WITH FORMAT, MEDIANAME = 'TestDB_MediaSet1' You can restore with something like: USE master GO RESTORE DATABASE TestDB FROM DISK = 'e:\backups\TestDB.bak' **WITH REPLACE** Check these links: Backups[^] Transaction Log Backups[^] Full Database Restore[^] I don't speak Idiot - please talk slowly and clearly 'This space for rent' Driven to the arms of Heineken by the wife

hvgyufg28fh38tyr78hf wrote: Could Some one tell me , is this results are right for this search? I'm not sure, but the documentation says that punctuation is ignored; Punctuation is ignored. I guess that you're searching for two separate terms in your query. Look through your resultset; there's 4 results that got either term. The source for this answer is here[^], under the heading "simple_term". Merry Christmas :thumbsup:

Yes but can i somehow incorporate MYSQL into my installation?

You could try xml also (sql 2005 and later i believe), its serializable and shouldn't be to difficult, but a table is the best way like the first response.

You have a begin tran on the outside of a while loop and have a rollback on the inside with an unconditional commit on the outside. If a rollback occurs, the loop continues transaction-less and the commit will execute anyway = your error 3902. I would not wrap a transaction around a while loop if there was another way (there is!). Never issue a commit or rollback without checking to see if there is actually a tran. if @@trancount > 0 rollback transaction I would use a try-catch, without a doubt. Heres generally how a transaction could be handled: begin try begin transaction --dml statement here if @@trancount > 0 commit transaction end try begin catch if @@trancount > 0 rollback transaction print error_message() --(execute my error handler) end catch Some of the other wierd messages you are getting is because the proc failed to issue a commit or rollback at all leaving 'things' in an un-committed state. Until you have verified that the proc you are developing will always close the trans - issue either a commit or rollback after each 'test'.

I am glad I could help. I like sqlite. My electronic document manager uses sqlite and it is much faster than my previous version (which used Microsoft Access).

Just in case anyone is interested, I solved the problem by replacing the SQL Express Server with the full version. All seems to be working correctly now.

You are Welcome :) Vuyiswa Maseko, Spoted in Daniweb-- Sorry to rant. I hate websites. They are just wierd. They don't behave like normal code. C#/VB.NET/ASP.NET/SQL7/2000/2005/2008 http://www.vuyiswamaseko.com vuyiswa@its.co.za http://www.itsabacus.co.za/itsabacus/

Try this declare @t table(somevalue varchar(100),startdate datetime, enddate datetime) insert into @t select 'somevalue1','01/14/2009', '01/20/2009' union all select 'somevalue2','01/15/2009', '01/22/2009' union all select 'somevalue3','01/18/2009', '01/31/2009' union all select 'somevalue4','02/01/2009', '02/10/2009' union all select 'somevalue5','05/14/2009', '05/20/2009' I want to get the records where between '01/14/2009' and '02/01/2009' (inclusive) Query: select * from @t where startdate >='01/14/2009' and enddate <='02/01/2009' Output: somevalue startdate enddate somevalue1 2009-01-14 00:00:00.000 2009-01-20 00:00:00.000 somevalue2 2009-01-15 00:00:00.000 2009-01-22 00:00:00.000 somevalue3 2009-01-18 00:00:00.000 2009-01-31 00:00:00.000 :) Niladri Biswas

Thanks a lot Mycroft. Listen up! "Teamwork" means staying out of my way! (Seifer, Final Fantasy 8).